All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuji Shimada <shimada-yxb@necst.nec.co.jp>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.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: Fri, 24 Apr 2009 17:38:24 +0900	[thread overview]
Message-ID: <20090424110406.B645.27C06F64@necst.nec.co.jp> (raw)
In-Reply-To: <C615ECDE.9492%keir.fraser@eu.citrix.com>

On Thu, 23 Apr 2009 10:01:02 +0100
Keir Fraser <keir.fraser@eu.citrix.com> wrote:

> On 23/04/2009 09:27, "Yuji Shimada" <shimada-yxb@necst.nec.co.jp> wrote:
> 
> > OK, I understand that my patches are also big. But I'm worried about
> > one problem for Xen 3.4. The problem is that devices are deassigned
> > before the reset on current Xen. Dom0 memory may be broken by DMA if
> > the problem is not fixed.
> > My patches fix the problem. I mean that devices are deassigned after
> > the reset with my patches.
> > 
> > I can work on making the patch just changing order of resetting/
> > deassigning devices if you need the fix for Xen 3.4.
> 
> If we stick with the existing pciback mechanisms and interfaces for 3.4
> (which is preferable at this point) will we simply break 3.4 branch as soon
> as the new pciback patches go into linux-2.6.18-xen when 3.5 opens? Or is
> there a story on backward compatibility between different pciback/xend
> versions?

Hi, Keir

I don't have any idea for backward compatibility between different
pciback/xend versions.
I give up being applied to linux-2.6.18-xen.

I will sent the patch to change the order of resetting/deassigning
device for Xen 3.4.

Thanks,
--
Yuji Shimada

  reply	other threads:[~2009-04-24  8:38 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
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 [this message]
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=20090424110406.B645.27C06F64@necst.nec.co.jp \
    --to=shimada-yxb@necst.nec.co.jp \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=Ross.Philipson@citrix.com \
    --cc=keir.fraser@eu.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.