From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] x86: eliminate x86_emulate's private EFLAGS definitions
Date: Tue, 19 Jun 2007 11:21:47 +0100 [thread overview]
Message-ID: <4677CA5B.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C29D6905.10DF2%Keir.Fraser@cl.cam.ac.uk>
>>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 19.06.07 12:05 >>>
>On 19/6/07 10:54, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>> .. in favor of using one of the two (i.e. already redundant) ones
>> found in the headers.
>>
>> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
>Currently x86_emulate is buildable 'out of tree', e.g., in tools/tests. I
>want to keep that ability but it is the case that down the line we'll be
>wanting more flags and structures to be sharable outside x86_emulate.c. I'm
>not sure yet what the right way of achieving that will be.
Yes, I was afraid of something like that (I just didn't know that I might be able
to build the thing in tools/tests, I thought this was completely out of tree, and
hence adding a local header would be possible).
In that light, perhaps doing a little cleanup on the headers having the desired
definitions, so that they can be included for the tool build, will do. I may find
some time to look into this possibility.
Jan
prev parent reply other threads:[~2007-06-19 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 9:54 [PATCH] x86: eliminate x86_emulate's private EFLAGS definitions Jan Beulich
2007-06-19 10:05 ` Keir Fraser
2007-06-19 10:21 ` Jan Beulich [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=4677CA5B.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.