xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] svm: Fix migration in the middle of a syscall
Date: Wed, 27 Jan 2010 14:38:56 +0000	[thread overview]
Message-ID: <C7860080.7892%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <201001271417.51234.Christoph.Egger@amd.com>

Looks like this is already handled in svm_{save,load}_cpu_state(). Did you
actually reproduce this bug?

 -- Keir

On 27/01/2010 13:17, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

> 
> Hi!
> 
> Attached patch fixes migration in the middle of a syscall.
> 
> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
> 
> Keir: Please also apply this patch to xen-3.4-testing.
> 

      reply	other threads:[~2010-01-27 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 13:17 [PATCH] svm: Fix migration in the middle of a syscall Christoph Egger
2010-01-27 14:38 ` Keir Fraser [this message]

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=C7860080.7892%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Christoph.Egger@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).