From: David Vrabel <david.vrabel@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: <konrad.wilk@oracle.com>, <xen-devel@lists.xenproject.org>,
<linux-kernel@vger.kernel.org>, <srostedt@redhat.com>,
<andrew.cooper3@citrix.com>, <JBeulich@suse.com>
Subject: Re: [PATCH v2] x86/xen: Fix 32-bit PV guests's usage of kernel_stack
Date: Tue, 15 Apr 2014 15:07:21 +0100 [thread overview]
Message-ID: <534D3D19.6000503@citrix.com> (raw)
In-Reply-To: <5346F588.8050707@oracle.com>
On 10/04/14 20:48, Boris Ostrovsky wrote:
>
> %fs is pointing to per-cpu segment so %fs:xen_vcpu should be different
> on each (V)CPU.
Oh yes, of course. Applied to stable/for-linus-3.15, thanks.
David
prev parent reply other threads:[~2014-04-15 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 16:17 [PATCH v2] x86/xen: Fix 32-bit PV guests's usage of kernel_stack Boris Ostrovsky
2014-04-10 18:20 ` David Vrabel
2014-04-10 19:48 ` Boris Ostrovsky
2014-04-15 14:07 ` David Vrabel [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=534D3D19.6000503@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srostedt@redhat.com \
--cc=xen-devel@lists.xenproject.org \
/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