From: Glauber Costa <glommer@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: mtosatti@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org,
avi@redhat.com
Subject: [Qemu-devel] Re: [PATCH 3/3] don't create kvmclock when one of the flags are present.
Date: Fri, 18 Mar 2011 11:29:04 -0300 [thread overview]
Message-ID: <1300458544.3137.284.camel@mothafucka.localdomain> (raw)
In-Reply-To: <4D8332F3.2090301@web.de>
On Fri, 2011-03-18 at 11:24 +0100, Jan Kiszka wrote:
> On 2011-03-17 23:42, Glauber Costa wrote:
> > kvmclock presence can be signalled by two different flags. So for
> > device creation, we have to test for both.
> Patch is OK, but the subject's logic is inverted.
Indeed, should have said something like "to test for either of them"
Dear maintainers, is it okay to commit with a minor edit to the
changelogs?
> Jan
>
> >
> > Signed-off-by: Glauber Costa <glommer@redhat.com>
> > ---
> > hw/kvmclock.c | 6 +++++-
> > 1 files changed, 5 insertions(+), 1 deletions(-)
> >
> > diff --git a/hw/kvmclock.c b/hw/kvmclock.c
> > index b6ceddf..004c4ad 100644
> > --- a/hw/kvmclock.c
> > +++ b/hw/kvmclock.c
> > @@ -103,7 +103,11 @@ static SysBusDeviceInfo kvmclock_info = {
> > void kvmclock_create(void)
> > {
> > if (kvm_enabled() &&
> > - first_cpu->cpuid_kvm_features & (1ULL << KVM_FEATURE_CLOCKSOURCE)) {
> > + first_cpu->cpuid_kvm_features & ((1ULL << KVM_FEATURE_CLOCKSOURCE)
> > +#ifdef KVM_FEATURE_CLOCKSOURCE2
> > + || (1ULL << KVM_FEATURE_CLOCKSOURCE2)
> > +#endif
> > + )) {
> > sysbus_create_simple("kvmclock", -1, NULL);
> > }
> > }
>
next prev parent reply other threads:[~2011-03-18 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 22:42 [Qemu-devel] [PATCH 0/3] enable newer msr set for kvm Glauber Costa
2011-03-17 22:42 ` [Qemu-devel] [PATCH 1/3] use kernel-provided para_features instead of statically coming up with new capabilities Glauber Costa
2011-03-24 10:27 ` [Qemu-devel] " Avi Kivity
2011-03-17 22:42 ` [Qemu-devel] [PATCH 2/3] add kvmclock to its second bit Glauber Costa
2011-03-17 22:42 ` [Qemu-devel] [PATCH 3/3] don't create kvmclock when one of the flags are present Glauber Costa
2011-03-18 10:24 ` [Qemu-devel] " Jan Kiszka
2011-03-18 14:29 ` Glauber Costa [this message]
2011-03-24 10:37 ` [Qemu-devel] Re: [PATCH 0/3] enable newer msr set for kvm Avi Kivity
2011-03-24 10:37 ` 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=1300458544.3137.284.camel@mothafucka.localdomain \
--to=glommer@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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 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).