From: Andi Kleen <ak@muc.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
Gerd Hoffmann <kraxel@suse.de>, Alan <alan@lxorguk.ukuu.org.uk>,
Ingo Molnar <mingo@elte.hu>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use X86_EFLAGS_IF in x86-64/irqflags.h.
Date: 30 Mar 2007 12:12:09 +0200
Date: Fri, 30 Mar 2007 12:12:09 +0200 [thread overview]
Message-ID: <20070330101209.GA79904@muc.de> (raw)
In-Reply-To: <1175224343.12230.368.camel@localhost.localdomain>
On Fri, Mar 30, 2007 at 01:12:23PM +1000, Rusty Russell wrote:
> On Thu, 2007-03-29 at 14:19 +0200, Andi Kleen wrote:
> > On Thu, Mar 29, 2007 at 09:06:57PM +1000, Rusty Russell wrote:
>
> [SNIP: processor-flags.h patch for i386 ]
>
> > Ok. Can you do it for x86-64 too?
>
> OK, here it is. Compiles, but -rc5-mm2 doesn't link for me on x86-64 at
> the moment.
What's the problem?
>
> Something seems quite wrong with CONFIG_X86_VSMP. AFAICT (1 << 18) is
> the "alignment check" flag, not the "virtual interrupt" flag which I
> expected.
They abuse that intentionally as a way to talk to their hypervisor.
You don't want to know details.
-Andi
next prev parent reply other threads:[~2007-03-30 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 7:46 [PATCH] ignore vgacon if hardware not present Rusty Russell
2007-03-29 10:36 ` Andi Kleen
2007-03-29 11:06 ` Rusty Russell
2007-03-29 12:19 ` Andi Kleen
2007-03-30 3:12 ` [PATCH] Use X86_EFLAGS_IF in x86-64/irqflags.h Rusty Russell
2007-03-30 10:12 ` Andi Kleen [this message]
2007-03-30 10:59 ` Rusty Russell
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=20070330101209.GA79904@muc.de \
--to=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeremy@xensource.com \
--cc=kraxel@suse.de \
--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