All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 02/04] qemu-kvm: Add header files for ia64.
Date: Mon, 04 May 2009 09:01:22 +0000	[thread overview]
Message-ID: <49FEAEE2.7040305@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC236A2BC05@pdsmsx503.ccr.corp.intel.com>

Jes Sorensen wrote:
> Zhang, Xiantao wrote:
>> Hi, Jes
>>     There should be no issue here.  You may refer to 
>> qemu-kvm/kvm/kernel/arch/x86/include/asm/kvm.h, and it also includes 
>> this stuff.  I remebered this stuff was used to solve the issues when 
>> uses kernel header files in userspace and the author should be Avi:-) 
>> You know, kernel header may include CONFIG_$ARCH macros but they are 
>> meaningless in userspace, so needs a way to solve the gap. But anyway 
>> we can do some cleanup or introduce new ways to solve the issue. Xiantao
>
> Hi Xiantao,
>
> I noticed it's in the x86 code as well - but I still think it's silly to
> add to the ia64 tree when we don't need it.
>
> Of course, Avi should fix up his headers too :-)
>

It's autogenerated; but we do need a cleaner solution.

qemu upstream is working on a more inclusive Linux header takeover; we 
can use that when it's done.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: "Zhang, Xiantao" <xiantao.zhang@intel.com>,
	"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 02/04] qemu-kvm: Add header files for ia64.
Date: Mon, 04 May 2009 12:01:22 +0300	[thread overview]
Message-ID: <49FEAEE2.7040305@redhat.com> (raw)
In-Reply-To: <49F82330.3090302@sgi.com>

Jes Sorensen wrote:
> Zhang, Xiantao wrote:
>> Hi, Jes
>>     There should be no issue here.  You may refer to 
>> qemu-kvm/kvm/kernel/arch/x86/include/asm/kvm.h, and it also includes 
>> this stuff.  I remebered this stuff was used to solve the issues when 
>> uses kernel header files in userspace and the author should be Avi:-) 
>> You know, kernel header may include CONFIG_$ARCH macros but they are 
>> meaningless in userspace, so needs a way to solve the gap. But anyway 
>> we can do some cleanup or introduce new ways to solve the issue. Xiantao
>
> Hi Xiantao,
>
> I noticed it's in the x86 code as well - but I still think it's silly to
> add to the ia64 tree when we don't need it.
>
> Of course, Avi should fix up his headers too :-)
>

It's autogenerated; but we do need a cleaner solution.

qemu upstream is working on a more inclusive Linux header takeover; we 
can use that when it's done.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  parent reply	other threads:[~2009-05-04  9:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  9:29 [PATCH 02/04] qemu-kvm: Add header files for ia64 Zhang, Xiantao
2009-04-28  9:29 ` Zhang, Xiantao
2009-04-29  9:30 ` Jes Sorensen
2009-04-29  9:30   ` Jes Sorensen
2009-04-29  9:44 ` Zhang, Xiantao
2009-04-29  9:44   ` Zhang, Xiantao
2009-04-29  9:51 ` Jes Sorensen
2009-04-29  9:51   ` Jes Sorensen
2009-04-29  9:57 ` Zhang, Xiantao
2009-04-29  9:57   ` Zhang, Xiantao
2009-05-04  9:01 ` Avi Kivity [this message]
2009-05-04  9:01   ` Avi Kivity

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=49FEAEE2.7040305@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm-ia64@vger.kernel.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.