All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] Import KVM headers including Makefile andimport script
Date: Sun, 03 May 2009 17:02:20 -0500	[thread overview]
Message-ID: <49FE146C.9060606@us.ibm.com> (raw)
In-Reply-To: <49FDB862.4040605@redhat.com>

Avi Kivity wrote:
> Anthony Liguori wrote:
>> These are the headers from Linux 2.6.29 that have been modified to 
>> work under
>> QEMU.  This includes the necessary scripts to generate the headers 
>> from the
>> original Linux source tree.
>>
>> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>> ---
>>  configure                      |    7 +-
>>  include/HEAD                   |    1 +
>>  include/Makefile               |   26 ++
>>  include/README                 |    6 +
>>  include/asm-powerpc/kvm.h      |   55 ++++
>>  include/asm-powerpc/kvm_para.h |   37 +++
>>  include/asm-x86/kvm.h          |  218 ++++++++++++++++
>>  include/asm-x86/kvm_para.h     |  147 +++++++++++
>>  include/fixup.sed              |   11 +
>>  include/linux/kvm.h            |  533 
>> ++++++++++++++++++++++++++++++++++++++++
>>  include/linux/kvm_para.h       |   44 ++++
>>   
>
> Another comment: let's add this as two separate commits, one for the 
> configure/Makefile and one for the actual headers.  The headers are 
> generated files, after all, so we should follow the procedures we use 
> for other generated files like the bios.
>
> It also makes the first commit easy to cherry-pick across branches and 
> repositories.

Sure.  As I mention in the newer README, I expect that we can track the 
kernel more closely as long as we're in a development branch (x.y.50).  
We just need to make sure that we use kernel releases for QEMU 
releases.  I think this should work out well for qemu-kvm.git too, right?

This new patch also implements the need for -D__user in CFLAGS FWIW.

-- 
Regards,

Anthony Liguori

      reply	other threads:[~2009-05-03 22:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-02 21:02 [Qemu-devel] [PATCH] Import KVM headers including Makefile and import script Anthony Liguori
2009-05-02 21:04 ` [Qemu-devel] " Anthony Liguori
2009-05-03  6:05 ` [Qemu-devel] " Avi Kivity
2009-05-03 15:06   ` [Qemu-devel] [PATCH] Import KVM headers including Makefile andimport script Anthony Liguori
2009-05-03 15:19     ` Avi Kivity
2009-05-03 21:59       ` [Qemu-devel] [PATCH] Import KVM headers including Makefile andimportscript Anthony Liguori
2009-05-04  7:59         ` Avi Kivity
2009-05-03 15:29 ` [Qemu-devel] [PATCH] Import KVM headers including Makefile and import script Avi Kivity
2009-05-03 22:02   ` Anthony Liguori [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=49FE146C.9060606@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=hollisb@us.ibm.com \
    --cc=qemu-devel@nongnu.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.