From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: gleb@redhat.com, kvm@vger.kernel.org, mtosatti@redhat.com,
qemu-devel@nongnu.org, Jan Kiszka <jan.kiszka@web.de>,
avi@redhat.com, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCHv2 1/4] linux-headers: update to 3.6-rc3
Date: Mon, 27 Aug 2012 17:50:05 +0300 [thread overview]
Message-ID: <20120827145005.GB779@redhat.com> (raw)
In-Reply-To: <CAFEAcA_-THP2FJgrhy4A8+bz5tTQaoOUtmQqfavR=hRXzA-rhw@mail.gmail.com>
On Mon, Aug 27, 2012 at 01:42:03PM +0100, Peter Maydell wrote:
> On 27 August 2012 13:20, Michael S. Tsirkin <mst@redhat.com> wrote:
> > Update linux-headers to version present in Linux 3.6-rc3.
> > Header asm-x96_64/kvm_para.h update is needed for the new PV EOI
> > feature.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > linux-headers/asm-s390/kvm.h | 2 +-
> > linux-headers/asm-s390/kvm_para.h | 2 +-
> > linux-headers/asm-x86/kvm.h | 1 +
> > linux-headers/asm-x86/kvm_para.h | 7 +++++++
> > linux-headers/linux/kvm.h | 3 +++
> > 5 files changed, 13 insertions(+), 2 deletions(-)
>
> The latest version of update-linux-headers.sh should have caused
> this update to include asm-generic/kvm_para.h, I think. Did the
> script not pull that header in, or were you maybe using an old
> version of the script or forgot to git add the new file?
>
> thanks
> -- PMM
I have no idea but adding new files is not the same as updating
existing ones.
Why don't you add it when you update headers to a version that
actually uses it?
--
MST
next prev parent reply other threads:[~2012-08-27 14:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 12:20 [Qemu-devel] [PATCHv2 0/4] migrate PV EOI MSR Michael S. Tsirkin
2012-08-27 12:20 ` [Qemu-devel] [PATCHv2 1/4] linux-headers: update to 3.6-rc3 Michael S. Tsirkin
2012-08-27 12:42 ` Peter Maydell
2012-08-27 12:48 ` Jan Kiszka
2012-08-27 14:53 ` Michael S. Tsirkin
2012-08-27 14:59 ` Jan Kiszka
2012-08-27 18:48 ` Michael S. Tsirkin
2012-08-27 14:50 ` Michael S. Tsirkin [this message]
2012-08-27 12:20 ` [Qemu-devel] [PATCHv2 2/4] pc: refactor compat code Michael S. Tsirkin
2012-08-28 16:23 ` Marcelo Tosatti
2012-08-28 16:31 ` Michael S. Tsirkin
2012-08-28 16:37 ` Marcelo Tosatti
2012-08-28 21:29 ` Michael S. Tsirkin
2012-08-27 12:20 ` [Qemu-devel] [PATCHv2 3/4] cpuid: disable pv eoi for 1.1 and older compat types Michael S. Tsirkin
2012-08-27 18:58 ` Blue Swirl
2012-08-27 19:06 ` Michael S. Tsirkin
2012-08-27 19:12 ` Blue Swirl
2012-08-27 19:24 ` Michael S. Tsirkin
2012-08-27 19:40 ` Blue Swirl
2012-08-28 15:46 ` Michael S. Tsirkin
2012-08-28 17:02 ` malc
2012-08-28 21:50 ` Michael S. Tsirkin
2012-08-28 19:13 ` Anthony Liguori
2012-08-28 19:40 ` Eduardo Habkost
2012-08-28 21:41 ` Michael S. Tsirkin
2012-08-28 21:40 ` Michael S. Tsirkin
2012-08-27 12:20 ` [Qemu-devel] [PATCHv2 4/4] kvm: get/set PV EOI MSR Michael S. Tsirkin
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=20120827145005.GB779@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).