From: "H. Peter Anvin" <hpa@zytor.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Kees Cook <kees.cook@canonical.com>,
matthieu castet <castet.matthieu@free.fr>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [BUG] broken ebba638ae723d8a8fc2f7abce5ec18b688b791d7
Date: Wed, 02 Feb 2011 18:35:44 -0800 [thread overview]
Message-ID: <3ba4a711-ac8b-46aa-b585-51c8b9881c8c@email.android.com> (raw)
In-Reply-To: <201102031230.13759.rusty@rustcorp.com.au>
Can we completely kill the "don't reload segments" flag, then?
"Rusty Russell" <rusty@rustcorp.com.au> wrote:
>On Thu, 3 Feb 2011 11:49:36 am Rusty Russell wrote:
>> On Thu, 3 Feb 2011 09:18:21 am H. Peter Anvin wrote:
>> > On 01/28/2011 08:58 AM, Jeremy Fitzhardinge wrote:
>> > > On 01/27/2011 07:38 PM, H. Peter Anvin wrote:
>> > >> [Adding Jeremy]
>> > >>
>> > >> Jeremy, would this break Xen? As far as I know, Xen is the main
>user
>> > >> of skipping segment register initialization.
>> > >
>> > > Xen doesn't go through head_*.S at all.
>> > >
>> >
>> > OK, I guess it's actually lguest which needs this feature?
>>
>> Well, we already move __BOOT_DS into every other segment reg, so I
>don't think
>> %ss will break...
>>
>> Checking...
>
>Fine here.
>
>Thanks,
>Rusty.
>PS. In general, I don't want lguest to interfere with cleanups: I'd
>rather
> fix up lguest as required until it gets too hard, then kill it.
--
Sent from my mobile phone. Please pardon any lack of formatting.
next prev parent reply other threads:[~2011-02-03 2:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 21:49 matthieu castet
2011-01-27 23:00 ` Kees Cook
2011-01-28 2:24 ` H. Peter Anvin
2011-01-28 3:38 ` H. Peter Anvin
2011-01-28 16:58 ` Jeremy Fitzhardinge
2011-02-02 22:48 ` H. Peter Anvin
2011-02-03 1:19 ` Rusty Russell
2011-02-03 2:00 ` Rusty Russell
2011-02-03 2:35 ` H. Peter Anvin [this message]
2011-02-03 10:02 ` Rusty Russell
2011-02-03 17:11 ` H. Peter Anvin
2011-01-31 21:38 ` Kees Cook
2011-01-31 23:11 ` matthieu castet
2011-01-31 23:17 ` Rafael J. Wysocki
2011-02-01 13:07 ` castet.matthieu
2011-02-01 18:50 ` Rafael J. Wysocki
2011-01-31 23:52 ` Kees Cook
2011-02-01 1:10 ` H. Peter Anvin
2011-02-02 20:40 ` Kees Cook
2011-02-04 5:47 ` H. Peter Anvin
2011-01-31 23:12 ` matthieu castet
2011-02-05 0:34 ` [tip:x86/urgent] x86-32: Make sure the stack is set up before we use it tip-bot for H. Peter Anvin
2011-02-05 0:45 ` tip-bot for H. Peter Anvin
2011-02-05 2:19 ` Kees Cook
2011-02-05 4:37 ` H. Peter Anvin
2011-02-05 5:37 ` Kees Cook
2011-02-05 6:26 ` H. Peter Anvin
2011-02-05 6:31 ` tip-bot for H. Peter Anvin
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=3ba4a711-ac8b-46aa-b585-51c8b9881c8c@email.android.com \
--to=hpa@zytor.com \
--cc=castet.matthieu@free.fr \
--cc=jeremy@goop.org \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/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®