All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuji Shimada <shimada-yxb@necst.nec.co.jp>
To: Ian Pratt <Ian.Pratt@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>,
	Kouya Shimura <kouya@jp.fujitsu.com>,
	Ross Philipson <Ross.Philipson@citrix.com>
Subject: Re: [PATCH 2/3] remove saving/restoring method in Xend.
Date: Thu, 23 Apr 2009 11:57:48 +0900	[thread overview]
Message-ID: <20090423115659.917F.27C06F64@necst.nec.co.jp> (raw)
In-Reply-To: <4FA716B1526C7C4DB0375C6DADBC4EA34172EC1DA5@LONPMAILBOX01.citrite.net>

On Wed, 22 Apr 2009 11:38:13 +0100
Ian Pratt <Ian.Pratt@eu.citrix.com> wrote:
> Does it not make sense to have pciback do the reset too? I think I've seen draft patches from Ross Philipson to move the reset into pciback -- they may even be checked in to the xenbits.xen.org/xenclient tree.

Hi, Ian

Of course, it is better to reset in pciback. So Ross's patches seems
to be nice. But as the future freeze is announced for Xen 3.4, I think
these patches are too big to merge with it. I think it is better to
merge these patches after Xen 3.4 is released.

My patches are sufficient enough to make Xen 3.4 robust in resetting/
restoring devices.

Thanks,
--
Yuji Shimada

  reply	other threads:[~2009-04-23  2:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22  2:11 [PATCH 0/3] save/restore PCI configuration space in pciback Yuji Shimada
2009-04-22  2:18 ` [PATCH 1/3] " Yuji Shimada
2009-04-22  2:20 ` [PATCH 2/3] remove saving/restoring method in Xend Yuji Shimada
2009-04-22  2:50   ` Masaki Kanno
2009-04-22  8:18     ` [PATCH 2/3 v2] " Yuji Shimada
2009-04-22 10:38   ` [PATCH 2/3] " Ian Pratt
2009-04-23  2:57     ` Yuji Shimada [this message]
2009-04-23  7:22       ` Keir Fraser
2009-04-23  8:27         ` Yuji Shimada
2009-04-23  9:01           ` Keir Fraser
2009-04-24  8:38             ` Yuji Shimada
2009-04-24  8:40             ` [PATCH 0/2] modify the order of resetting/deassigning device Yuji Shimada
2009-04-24  8:43               ` [PATCH 1/2] " Yuji Shimada
2009-04-24  8:43               ` [PATCH 2/2] ioemu: don't call xc_deassign_device() Yuji Shimada
2009-04-28  6:02                 ` Yuji Shimada
2009-04-22  2:20 ` [PATCH 3/3] ioemu: remove power state transition and xc_deassign_device() Yuji Shimada

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090423115659.917F.27C06F64@necst.nec.co.jp \
    --to=shimada-yxb@necst.nec.co.jp \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=Ross.Philipson@citrix.com \
    --cc=kouya@jp.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.