From: Eduardo Habkost <ehabkost@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [maint/2.6.29 PATCH] kvm-userspace: include <asm/svm.h> on external-module-compat.h
Date: Wed, 4 Feb 2009 20:39:31 -0200 [thread overview]
Message-ID: <20090204223931.GR5336@blackpad> (raw)
In-Reply-To: <4989A5E3.2060604@redhat.com>
On Wed, Feb 04, 2009 at 04:27:47PM +0200, Avi Kivity wrote:
> Eduardo Habkost wrote:
>> Make sure we get the MSR_* defines from asm/svm.h before checking
>> if they are defined.
>>
>> This fixes the following warning:
>>
>> In file included from /home/ehabkost/code/kvm/kvm-userspace/kernel/x86/kvm_svm.h:10,
>> from /home/ehabkost/code/kvm/kvm-userspace/kernel/x86/svm.c:58:
>> /home/ehabkost/code/kvm/kvm-userspace/kernel/include/asm/svm.h:219:1: warning: "MSR_VM_HSAVE_PA" redefined
>>
>>
>> This fix applies only to the maint/2.6.29 branch, as on the master
>> branch the MSR_* defines went to a different header file.
>>
>
> I fixed this on master with d3898e3aaef791fac527d4cf4fc5b898887abc38.
> Any reason not to apply the same fix to maint?
That's a different problem. The warning I'm seeing doesn't involve
msr-index.h (either the real one or the compat one).
My fix applies only to maint/2.6.29 because on master
the MSR_* defines were moved to asm/msr-index.h (by
dd29b0ddd904e19b7744055f1ee386ad9a8cf13d), and asm/msr-index.h is already
(indirectly) included by external-module-compat.h before the #ifdefs. On
maint/2.6.29, the #defines are still on asm/svm.h.
Cherry-picking dd29b0ddd904e19b7744055f1ee386ad9a8cf13d
(moves the defines to msr-index.h) on kvm.git maint/2.6.29 and
d3898e3aaef791fac527d4cf4fc5b898887abc38 (the fix needed after the move)
on kvm-userspace.git maint/2.6.29 would work, also.
--
Eduardo
prev parent reply other threads:[~2009-02-04 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 20:59 [maint/2.6.29 PATCH] kvm-userspace: include <asm/svm.h> on external-module-compat.h Eduardo Habkost
2009-02-04 14:27 ` Avi Kivity
2009-02-04 22:39 ` Eduardo Habkost [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=20090204223931.GR5336@blackpad \
--to=ehabkost@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox