xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: AndrewCooper <andrew.cooper3@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 04/12] x86emul/test: use x86-vendors.h
Date: Tue, 31 Jan 2017 15:16:55 +0000	[thread overview]
Message-ID: <20170131151655.xpjc2ylbulquuimu@citrix.com> (raw)
In-Reply-To: <5890B8400200007800135867@prv-mh.provo.novell.com>

On Tue, Jan 31, 2017 at 08:16:00AM -0700, Jan Beulich wrote:
> >>> On 31.01.17 at 15:36, <wei.liu2@citrix.com> wrote:
> > On Tue, Jan 31, 2017 at 05:50:09AM -0700, Jan Beulich wrote:
> >> >>> On 31.01.17 at 12:08, <wei.liu2@citrix.com> wrote:
> >> > --- a/tools/tests/x86_emulator/x86_emulate.h
> >> > +++ b/tools/tests/x86_emulator/x86_emulate.h
> >> > @@ -6,6 +6,8 @@
> >> >  #include <string.h>
> >> >  #include <xen/xen.h>
> >> >  
> >> > +#include "../../../xen/include/asm-x86/x86-vendors.h"
> >> 
> >> I think we'd better avoid includes of this style. May I suggest
> >> symlinking the needed headers, just like we already do with the
> >> x86_emulate/x86_emulate[ch] files (perhaps to an include/
> >> subdirectory in the build tree)?
> > 
> > I will just link this (and later headers) to tools/tests/x86_emulator --
> > using a dedicated directory is not strictly necessary.
> 
> Hmm, for consistency with hypervisor #include directives, linking
> to asm/ (and adding -I. to CFLAGS) might be a good idea.
> 

Sure, I don't feel strongly about this.

Wei.

> Jan
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-01-31 15:17 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 11:07 [PATCH v2 00/12] fuzz: update x86emul fuzzer Wei Liu
2017-01-31 11:07 ` [PATCH v2 01/12] fuzz: don't buffer stdout in afl stubs Wei Liu
2017-01-31 12:44   ` Jan Beulich
2017-01-31 11:07 ` [PATCH v2 02/12] x86: extract macros to x86-defns.h Wei Liu
2017-01-31 12:45   ` Jan Beulich
2017-01-31 13:28     ` Wei Liu
2017-01-31 11:08 ` [PATCH v2 03/12] x86: extract vendor numeric id to x86-vendors.h Wei Liu
2017-01-31 12:48   ` Jan Beulich
2017-01-31 11:08 ` [PATCH v2 04/12] x86emul/test: use x86-vendors.h Wei Liu
2017-01-31 12:50   ` Jan Beulich
2017-01-31 14:36     ` Wei Liu
2017-01-31 15:16       ` Jan Beulich
2017-01-31 15:16         ` Wei Liu [this message]
2017-01-31 11:08 ` [PATCH v2 05/12] x86emul: use eflags definitions in x86-defns.h Wei Liu
2017-01-31 12:56   ` Jan Beulich
2017-01-31 14:55     ` Wei Liu
2017-01-31 15:16       ` Jan Beulich
2017-01-31 11:08 ` [PATCH v2 06/12] x86emul: use msr definitions in msr-index.h Wei Liu
2017-01-31 12:59   ` Jan Beulich
2017-01-31 11:08 ` [PATCH v2 07/12] x86: add UMIP CR4 bit Wei Liu
2017-01-31 13:00   ` Jan Beulich
2017-01-31 11:08 ` [PATCH v2 08/12] x86emul: use CR definitions in x86-defns.h Wei Liu
2017-01-31 13:01   ` Jan Beulich
2017-01-31 11:08 ` [PATCH v2 09/12] x86emul: use TRAP " Wei Liu
2017-01-31 11:26   ` Andrew Cooper
2017-01-31 11:08 ` [PATCH v2 10/12] fuzz/x86emul: update fuzzer Wei Liu
2017-01-31 13:33   ` Jan Beulich
2017-01-31 15:51     ` Wei Liu
2017-01-31 15:57       ` Andrew Cooper
2017-01-31 16:01         ` George Dunlap
2017-01-31 16:05         ` Jan Beulich
2017-01-31 16:02       ` Jan Beulich
2017-01-31 17:37         ` Wei Liu
2017-01-31 11:08 ` [PATCH v2 11/12] fuzz/x86emul: print out minimal input size Wei Liu
2017-01-31 13:33   ` Jan Beulich
2017-01-31 11:08 ` [PATCH v2 12/12] fuzz: update README.afl example Wei Liu
2017-01-31 13:34   ` Jan Beulich

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=20170131151655.xpjc2ylbulquuimu@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).