From: Paolo Bonzini <pbonzini@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH v6 6/6] KVM: Use eoi to track RTC interrupt delivery status
Date: Tue, 26 Mar 2013 15:26:21 +0100 [thread overview]
Message-ID: <5151B00D.1050700@redhat.com> (raw)
In-Reply-To: <20130322085434.GS9382@redhat.com>
Il 22/03/2013 09:54, Gleb Natapov ha scritto:
>>>> > >>
>>> > > If userspace does not care about irq status it does not use IRQ_STATUS
>>> > > ioctl and we should not go extra mile to provide one. Not everyone cares
>>> > > about running Windows as a guest.
>> > I see your point. But if no windows guest running, RTC is hardly used by other guests and the overheard can be ignore.
>> >
> Anyone can use RTC is Linux guest. Don't know about others.
I do not think the additional code complexity is worth the speedup.
The KVM Userspace That Won't Be Merged doesn't even emulate the RTC
interrupt at all.
Paolo
next prev parent reply other threads:[~2013-03-26 14:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 5:23 [PATCH v6 0/6] Use eoi to track RTC interrupt delivery status Yang Zhang
2013-03-22 5:24 ` [PATCH v6 1/6] KVM: Add vcpu info to ioapic_update_eoi() Yang Zhang
2013-03-22 5:24 ` [PATCH v6 2/6] KVM: Introduce struct rtc_status Yang Zhang
2013-03-22 5:24 ` [PATCH v6 3/6] KVM : Return destination vcpu on interrupt injection Yang Zhang
2013-03-22 7:05 ` Gleb Natapov
2013-03-22 7:50 ` Zhang, Yang Z
2013-03-22 7:57 ` Gleb Natapov
2013-03-22 5:24 ` [PATCH v6 4/6] KVM: Add reset/restore rtc_status support Yang Zhang
2013-03-26 14:04 ` Paolo Bonzini
2013-03-29 3:17 ` Zhang, Yang Z
2013-03-26 14:09 ` Paolo Bonzini
2013-03-29 3:19 ` Zhang, Yang Z
2013-03-22 5:24 ` [PATCH v6 5/6] KVM : Force vmexit with virtual interrupt delivery Yang Zhang
2013-03-22 5:24 ` [PATCH v6 6/6] KVM: Use eoi to track RTC interrupt delivery status Yang Zhang
2013-03-22 7:50 ` Gleb Natapov
2013-03-22 8:05 ` Zhang, Yang Z
2013-03-22 8:14 ` Gleb Natapov
2013-03-22 8:25 ` Zhang, Yang Z
2013-03-22 8:30 ` Gleb Natapov
2013-03-22 8:37 ` Zhang, Yang Z
2013-03-22 8:44 ` Gleb Natapov
2013-03-22 8:51 ` Zhang, Yang Z
2013-03-22 8:54 ` Gleb Natapov
2013-03-22 10:50 ` Zhang, Yang Z
2013-03-24 9:20 ` Gleb Natapov
2013-03-26 14:26 ` Paolo Bonzini [this message]
2013-03-26 14:14 ` Paolo Bonzini
2013-03-29 3:25 ` Zhang, Yang Z
2013-03-29 8:35 ` Paolo Bonzini
2013-03-29 8:42 ` Zhang, Yang Z
2013-04-02 13:08 ` Gleb Natapov
2013-04-03 0:21 ` Zhang, Yang Z
2013-04-03 4:03 ` Gleb Natapov
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=5151B00D.1050700@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiantao.zhang@intel.com \
--cc=yang.z.zhang@intel.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.