public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: avi@redhat.com, mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCHv3 0/4] Add support for some HYPER-V PV features
Date: Tue, 19 Jan 2010 12:41:56 +0100	[thread overview]
Message-ID: <4B559A84.1040509@siemens.com> (raw)
In-Reply-To: <1263736284-18780-1-git-send-email-gleb@redhat.com>

Gleb Natapov wrote:
> HYPER-V provides PV capabilities for its guests and most new MS Windows
> detect and use them automatically. Older Windows guests need additional
> drivers to uses PV. This patch series implements some PV capabilities
> defined by HYPER-V spec for KVM. Windows guests running on KVM will be
> able to take advantage of them.
> 

This series generates warnings on 32-bit hosts. I'm currently busy with
more critical problems, maybe you can already have a look.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2010-01-19 11:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17 13:51 [PATCHv3 0/4] Add support for some HYPER-V PV features Gleb Natapov
2010-01-17 13:51 ` [PATCHv3 1/4] Add HYPER-V header file Gleb Natapov
2010-01-17 13:51 ` [PATCHv3 2/4] Implement bare minimum of HYPER-V MSRs Gleb Natapov
2010-01-17 13:51 ` [PATCHv3 3/4] Add HYPER-V apic access MSRs Gleb Natapov
2010-01-17 13:51 ` [PATCHv3 4/4] Implement NotifyLongSpinWait HYPER-V hypercall Gleb Natapov
2010-01-17 13:59 ` [PATCHv3 0/4] Add support for some HYPER-V PV features Avi Kivity
2010-01-19 11:41 ` Jan Kiszka [this message]
2010-01-19 12:50   ` Gleb Natapov
2010-01-19 12:53     ` Avi Kivity
2010-01-19 13:06       ` Gleb Natapov
2010-01-19 14:54         ` Marcelo Tosatti

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=4B559A84.1040509@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox