From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@web.de>, qemu-trivial <qemu-trivial@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-trivial] [PATCH] apic: Fix reported DFR content
Date: Wed, 13 Aug 2014 10:14:40 +0400 [thread overview]
Message-ID: <53EB0250.4080007@msgid.tls.msk.ru> (raw)
In-Reply-To: <53E62ABF.2000104@web.de>
09.08.2014 18:05, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> IA-32 SDM, Figure 10-14: Bits 27:0 are reserved as 1.
>
> Fixes Jailhouse hypervisor start with in-kernel irqchips off.
Applied to -trivial, thank you!
Are the other similar cases in there okay?
Say, 0x0d or 0x02 which also uses shifts like this one?
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@web.de>, qemu-trivial <qemu-trivial@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] apic: Fix reported DFR content
Date: Wed, 13 Aug 2014 10:14:40 +0400 [thread overview]
Message-ID: <53EB0250.4080007@msgid.tls.msk.ru> (raw)
In-Reply-To: <53E62ABF.2000104@web.de>
09.08.2014 18:05, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> IA-32 SDM, Figure 10-14: Bits 27:0 are reserved as 1.
>
> Fixes Jailhouse hypervisor start with in-kernel irqchips off.
Applied to -trivial, thank you!
Are the other similar cases in there okay?
Say, 0x0d or 0x02 which also uses shifts like this one?
/mjt
next prev parent reply other threads:[~2014-08-13 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 14:05 [Qemu-trivial] [PATCH] apic: Fix reported DFR content Jan Kiszka
2014-08-09 14:05 ` [Qemu-devel] " Jan Kiszka
2014-08-13 6:14 ` Michael Tokarev [this message]
2014-08-13 6:14 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2014-08-13 7:09 ` Jan Kiszka
2014-08-13 7:09 ` [Qemu-devel] " Jan Kiszka
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=53EB0250.4080007@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=jan.kiszka@web.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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.