All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: mtosatti@redhat.com, pl@dlhnet.de, qemu-devel@nongnu.org,
	aliguori@amazon.com
Subject: Re: [Qemu-devel] [PATCH 3/3] add support for hyperv time parameter
Date: Wed, 22 Jan 2014 11:02:23 +0100	[thread overview]
Message-ID: <52DF972F.3080705@redhat.com> (raw)
In-Reply-To: <1390338775.22984.24.camel@w7-rhel>

Il 21/01/2014 22:12, Vadim Rozenfeld ha scritto:
>> >
>> > If you are planning some level of backwards compatibility with RHEL6, it
>> > may make sense to use separate subsections.
> I believe we have to make it backward compatible. In RHEL6 we added
> support for relaxed timers only, but upstream doesn't have such bits.
> Technically, hypercall page, vapic and iTSC pages will be introduced in
> RHEL7 and as you said, they will probably go to a different, new
> section, but for upstream the entire section is absolutely new.

Ok, then upstream we have choice.  Using 2 subsections is not wrong, and 
it makes sense since it's covered by different kernel capabilities.

Paolo

      reply	other threads:[~2014-01-22 10:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21  8:02 [Qemu-devel] [PATCH 0/3] Hyper-V parameters Vadim Rozenfeld
2014-01-21  8:02 ` [Qemu-devel] [PATCH 1/3] cleanup hyper-v interface initialization Vadim Rozenfeld
2014-01-21 10:14   ` Paolo Bonzini
2014-01-21  8:02 ` [Qemu-devel] [PATCH 2/3] make hyperv hypercall, vapic, and os id MSRs migratable Vadim Rozenfeld
2014-01-21 10:17   ` Paolo Bonzini
2014-01-21  8:02 ` [Qemu-devel] [PATCH 3/3] add support for hyperv time parameter Vadim Rozenfeld
2014-01-21 10:21   ` Paolo Bonzini
2014-01-21 21:12     ` Vadim Rozenfeld
2014-01-22 10:02       ` Paolo Bonzini [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=52DF972F.3080705@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=mtosatti@redhat.com \
    --cc=pl@dlhnet.de \
    --cc=qemu-devel@nongnu.org \
    --cc=vrozenfe@redhat.com \
    /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.