From: Paolo Bonzini <pbonzini@redhat.com>
To: asmetanin@virtuozzo.com, kvm@vger.kernel.org
Cc: Gleb Natapov <gleb@kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
qemu-devel@nongnu.org, Roman Kagan <rkagan@virtuozzo.com>,
"Denis V. Lunev" <den@openvz.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
"K. Y. Srinivasan" <kys@microsoft.com>
Subject: Re: [Qemu-devel] [PATCH v1 6/7] kvm/x86: Hyper-V SynIC message slot pending clearing at SINT ack
Date: Wed, 25 Nov 2015 18:14:43 +0100 [thread overview]
Message-ID: <5655EC83.4090201@redhat.com> (raw)
In-Reply-To: <5655E800.5030309@virtuozzo.com>
On 25/11/2015 17:55, Andrey Smetanin wrote:
>>
>> + gpa = synic->msg_page & PAGE_MASK;
>> + page = kvm_vcpu_gfn_to_page(vcpu, gpa >> PAGE_SHIFT);
>> + if (is_error_page(page)) {
>> + vcpu_err(vcpu, "Hyper-V SynIC can't get msg page, gpa 0x%llx\n",
>> + gpa);
>> + return;
>> + }
>> + msg_page = kmap_atomic(page);
>
> But the message page is not being pinned, is it?
>
> Actually I don't know anything about pinning.
> Is it pinning against page swapping ?
Yes. Unless the page is pinned, kmap_atomic can fail.
However, I don't think that kvm_hv_notify_acked_sint is called from
atomic context. It is only called from apic_set_eoi. Could you just
use kvm_vcpu_write_guest_page?
By the way, do you need to do this also in kvm_get_apic_interrupt, for
auto EOI interrupts?
Thanks,
Paolo
> Could you please clarify and provide an API to use in this case ?
next prev parent reply other threads:[~2015-11-25 17:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 15:20 [Qemu-devel] [PATCH v1 0/7] KVM: Hyper-V SynIC timers Andrey Smetanin
2015-11-25 15:20 ` [Qemu-devel] [PATCH v1 1/7] drivers/hv: Move HV_SYNIC_STIMER_COUNT into Hyper-V UAPI x86 header Andrey Smetanin
2015-11-27 17:27 ` KY Srinivasan
2015-11-25 15:20 ` [Qemu-devel] [PATCH v1 2/7] drivers/hv: Move struct hv_message into UAPI Hyper-V " Andrey Smetanin
2015-11-27 9:34 ` Paolo Bonzini
2015-11-27 11:21 ` Andrey Smetanin
2015-11-27 17:34 ` KY Srinivasan
2015-11-25 15:20 ` [Qemu-devel] [PATCH v1 3/7] kvm/x86: Rearrange func's declarations inside Hyper-V header Andrey Smetanin
2015-11-25 15:20 ` [Qemu-devel] [PATCH v1 4/7] kvm/x86: Added Hyper-V vcpu_to_hv_vcpu()/hv_vcpu_to_vcpu() helpers Andrey Smetanin
2015-11-25 15:20 ` [Qemu-devel] [PATCH v1 5/7] kvm/x86: Hyper-V internal helper to read MSR HV_X64_MSR_TIME_REF_COUNT Andrey Smetanin
2015-11-25 15:20 ` [Qemu-devel] [PATCH v1 6/7] kvm/x86: Hyper-V SynIC message slot pending clearing at SINT ack Andrey Smetanin
2015-11-25 16:52 ` Paolo Bonzini
2015-11-25 16:55 ` Andrey Smetanin
2015-11-25 17:14 ` Paolo Bonzini [this message]
2015-11-26 9:06 ` Andrey Smetanin
2015-11-26 14:43 ` Paolo Bonzini
2015-11-26 15:53 ` Andrey Smetanin
2015-11-26 15:56 ` Paolo Bonzini
2015-11-27 8:16 ` Roman Kagan
2015-11-25 15:20 ` [Qemu-devel] [PATCH v1 7/7] kvm/x86: Hyper-V SynIC timers Andrey Smetanin
2015-11-27 8:12 ` Roman Kagan
2015-11-27 10:49 ` Paolo Bonzini
2015-11-27 11:24 ` Andrey Smetanin
2015-11-30 12:17 ` Roman Kagan
2015-11-26 5:28 ` [Qemu-devel] [PATCH v1 0/7] KVM: " Wanpeng Li
2015-11-26 8:34 ` Andrey Smetanin
2015-11-26 9:03 ` Wanpeng Li
2015-12-01 10:12 ` Wanpeng Li
2015-12-01 10:28 ` Denis V. Lunev
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=5655EC83.4090201@redhat.com \
--to=pbonzini@redhat.com \
--cc=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=gleb@kernel.org \
--cc=haiyangz@microsoft.com \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.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 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).