From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Andy Lutomirski <luto@amacapital.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] x86_64,xen,espfix: Initialize espfix on secondary CPUs
Date: Tue, 15 Jul 2014 11:45:36 -0400 [thread overview]
Message-ID: <53C54CA0.1060904@oracle.com> (raw)
In-Reply-To: <20140715153801.GX3403@laptop.dumpdata.com>
On 07/15/2014 11:38 AM, Konrad Rzeszutek Wilk wrote:
> On Tue, Jul 15, 2014 at 08:26:41AM -0700, Andy Lutomirski wrote:
>> Xen doesn't call start_secondary.
> Duh!
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Andy Lutomirski <luto@amacapital.net>
>> ---
>>
>> espfix still doesn't seem to work on Xen (it goes boom in some way that
>> I don't understand right now), but initializing all CPUs instead of just
>> one of them seems like a good start.
>>
>> ISTM the right fix is probably to shove the espfix logic into
>> native_iret and to tweak the paravirt logic so that native_iret always
>> gets invoked. I suspect that Xen will need its own implementation of
>> espfix64 in the hypervisor and that, ultimately, someone may want to
>> stop initializing espfix64 at all on Xen guests.
> I think just disallowing would be preferrable.
I've been looking at sigreturn_64 and it seems to be crashing dom0 (with
both mine and your patches). In kprobe_int3_handler().
-boris
>
> Thanks for posting this patch!
>> arch/x86/xen/smp.c | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/arch/x86/xen/smp.c b/arch/x86/xen/smp.c
>> index 7005974..eea9bcc 100644
>> --- a/arch/x86/xen/smp.c
>> +++ b/arch/x86/xen/smp.c
>> @@ -23,6 +23,7 @@
>> #include <asm/desc.h>
>> #include <asm/pgtable.h>
>> #include <asm/cpu.h>
>> +#include <asm/espfix.h>
>>
>> #include <xen/interface/xen.h>
>> #include <xen/interface/vcpu.h>
>> @@ -85,6 +86,13 @@ static void cpu_bringup(void)
>>
>> xen_setup_cpu_clockevents();
>>
>> + /*
>> + * Enable the espfix hack for this CPU
>> + */
>> +#ifdef CONFIG_X86_ESPFIX64
>> + init_espfix_ap();
>> +#endif
>> +
>> notify_cpu_starting(cpu);
>>
>> set_cpu_online(cpu, true);
>> --
>> 1.9.3
>>
next prev parent reply other threads:[~2014-07-15 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 15:26 Andy Lutomirski
2014-07-15 15:38 ` Konrad Rzeszutek Wilk
2014-07-15 15:44 ` Andy Lutomirski
2014-07-15 15:56 ` Konrad Rzeszutek Wilk
2014-07-15 15:45 ` Boris Ostrovsky [this message]
2014-07-15 15:54 ` Andy Lutomirski
2014-07-15 16:05 ` Boris Ostrovsky
2014-07-15 16:17 ` Andy Lutomirski
2014-07-15 15:50 ` H. Peter Anvin
2014-07-15 16:00 ` Andy Lutomirski
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=53C54CA0.1060904@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®