All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
	linux-kernel@vger.kernel.org,
	"Roman Kagan" <rkagan@virtuozzo.com>
Subject: Re: [PATCH v2 0/2] x86/kvm/hyper-v: Direct Mode stimers fixes
Date: Fri, 14 Dec 2018 11:53:37 +0100	[thread overview]
Message-ID: <4e126f47-88aa-9d32-daaa-de1e4363cff7@redhat.com> (raw)
In-Reply-To: <20181212165017.13278-1-vkuznets@redhat.com>

On 12/12/18 17:50, Vitaly Kuznetsov wrote:
> Changes in v2:
> - PATCH2 added [Roman Kagan]
> 
> This is a follow-up to my "x86/kvm/hyper-v: direct mode for synthetic
> timers" series. Roman identified a couple of issues with the patchset:
> we don't check that the supplied APIC vector is valid and we care about
> EOI for nothing. These can be merged with the original patch implementing
> direct mode stimers or just put on top.
> 
> Vitaly Kuznetsov (2):
>   x86/hyper-v: Stop caring about EOI for direct stimers
>   x86/kvm/hyper-v: disallow setting illegal vectors for direct mode
>     stimers
> 
>  arch/x86/kvm/hyperv.c | 41 ++++++++---------------------------------
>  1 file changed, 8 insertions(+), 33 deletions(-)
> 

Queued, thanks.

Paolo

      parent reply	other threads:[~2018-12-14 10:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 16:50 [PATCH v2 0/2] x86/kvm/hyper-v: Direct Mode stimers fixes Vitaly Kuznetsov
2018-12-12 16:50 ` [PATCH v2 1/2] x86/hyper-v: Stop caring about EOI for direct stimers Vitaly Kuznetsov
2018-12-13 12:17   ` Roman Kagan
2018-12-12 16:50 ` [PATCH v2 2/2] x86/kvm/hyper-v: disallow setting illegal vectors for direct mode stimers Vitaly Kuznetsov
2018-12-13 12:18   ` Roman Kagan
2018-12-14 10:53 ` 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=4e126f47-88aa-9d32-daaa-de1e4363cff7@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkagan@virtuozzo.com \
    --cc=rkrcmar@redhat.com \
    --cc=vkuznets@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.