From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xen: clean up x86-64 warnings
Date: Fri, 3 Oct 2008 10:04:30 +0200 [thread overview]
Message-ID: <20081003080428.GD25408@elte.hu> (raw)
In-Reply-To: <48E55C2B.1060804@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> There are a couple of Xen features which rely on directly accessing
> per-cpu data via a segment register, which is not yet available on
> x86-64. In the meantime, just disable direct access to the vcpu info
> structure; this leaves some of the code as dead, but it will come to
> life in time, and the warnings are suppressed.
>
> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> ---
> arch/x86/xen/enlighten.c | 61 +++++++--------------------------------------
> arch/x86/xen/xen-asm_64.S | 22 +++++++++++++---
> 2 files changed, 28 insertions(+), 55 deletions(-)
applied to tip/x86/xen, thanks Jeremy!
Ingo
prev parent reply other threads:[~2008-10-03 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 23:41 [PATCH] xen: clean up x86-64 warnings Jeremy Fitzhardinge
2008-10-03 8:04 ` Ingo Molnar [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=20081003080428.GD25408@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.