From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: X86 <x86@kernel.org>, Jeremy Fitzhardinge <jeremy@goop.org>,
Greg Kroah-Hartman <gregkh@suse.de>, KVM <kvm@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
Virtualization <virtualization@lists.linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Sasha Levin <levinsasha928@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Xen <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH RFC V6 1/5] kvm hypervisor : Add a hypercall to KVM hypervisor to support pv-ticketlocks
Date: Sun, 29 Apr 2012 16:26:21 +0300 [thread overview]
Message-ID: <4F9D417D.1050105@redhat.com> (raw)
In-Reply-To: <20120429132030.GB15413@redhat.com>
On 04/29/2012 04:20 PM, Gleb Natapov wrote:
> > > This is too similar to kvm_irq_delivery_to_apic(). Why not reuse it. We
> > > can use one of reserved delivery modes as PV delivery mode. We will
> > > disallow guest to trigger it through apic interface, so this will not be
> > > part of ABI and can be changed at will.
> > >
> >
> > I'm not thrilled about this. Those delivery modes will eventually
> > become unreserved. We can have a kvm_lookup_apic_id() that is shared
> > among implementations.
> >
> This is only internal implementation. If they become unreserved we will
> use something else.
>
Yeah, I'm thinking of that time. Why do something temporary and fragile?
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Alexander Graf <agraf@suse.de>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-doc@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
KVM <kvm@vger.kernel.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Virtualization <virtualization@lists.linux-foundation.org>,
X86 <x86@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Xen <xen-devel@lists.xensource.com>,
Sasha Levin <levinsasha928@gmail.com>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Subject: Re: [PATCH RFC V6 1/5] kvm hypervisor : Add a hypercall to KVM hypervisor to support pv-ticketlocks
Date: Sun, 29 Apr 2012 16:26:21 +0300 [thread overview]
Message-ID: <4F9D417D.1050105@redhat.com> (raw)
In-Reply-To: <20120429132030.GB15413@redhat.com>
On 04/29/2012 04:20 PM, Gleb Natapov wrote:
> > > This is too similar to kvm_irq_delivery_to_apic(). Why not reuse it. We
> > > can use one of reserved delivery modes as PV delivery mode. We will
> > > disallow guest to trigger it through apic interface, so this will not be
> > > part of ABI and can be changed at will.
> > >
> >
> > I'm not thrilled about this. Those delivery modes will eventually
> > become unreserved. We can have a kvm_lookup_apic_id() that is shared
> > among implementations.
> >
> This is only internal implementation. If they become unreserved we will
> use something else.
>
Yeah, I'm thinking of that time. Why do something temporary and fragile?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-04-29 13:26 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 9:59 [PATCH RFC V6 0/5] kvm : Paravirt-spinlock support for KVM guests Raghavendra K T
2012-04-23 9:59 ` Raghavendra K T
2012-04-23 9:59 ` [PATCH RFC V6 1/5] kvm hypervisor : Add a hypercall to KVM hypervisor to support pv-ticketlocks Raghavendra K T
2012-04-23 9:59 ` Raghavendra K T
2012-04-24 9:59 ` Gleb Natapov
2012-04-24 9:59 ` Gleb Natapov
2012-04-26 8:11 ` Raghavendra K T
2012-04-26 8:11 ` Raghavendra K T
2012-04-27 10:45 ` Raghavendra K T
2012-04-27 10:45 ` Raghavendra K T
2012-04-27 15:53 ` Gleb Natapov
2012-04-27 15:53 ` Gleb Natapov
2012-06-28 18:17 ` Raghavendra K T
2012-06-28 18:17 ` Raghavendra K T
2012-04-29 13:18 ` Avi Kivity
2012-04-29 13:18 ` Avi Kivity
2012-04-29 13:20 ` Gleb Natapov
2012-04-29 13:20 ` Gleb Natapov
2012-04-29 13:26 ` Avi Kivity [this message]
2012-04-29 13:26 ` Avi Kivity
2012-04-29 13:52 ` Gleb Natapov
2012-04-29 13:52 ` Gleb Natapov
2012-04-30 8:22 ` Avi Kivity
2012-04-30 8:22 ` Avi Kivity
2012-04-30 8:38 ` Gleb Natapov
2012-04-30 8:38 ` Gleb Natapov
2012-04-29 13:25 ` Avi Kivity
2012-04-29 13:25 ` Avi Kivity
2012-04-30 7:44 ` Raghavendra K T
2012-04-30 7:44 ` Raghavendra K T
2012-04-30 8:19 ` Avi Kivity
2012-04-30 8:19 ` Avi Kivity
2012-05-01 20:20 ` Raghavendra K T
2012-05-01 20:20 ` Raghavendra K T
2012-04-23 10:00 ` [PATCH RFC V6 2/5] kvm : Fold pv_unhalt flag into GET_MP_STATE ioctl to aid migration Raghavendra K T
2012-04-29 13:27 ` Avi Kivity
2012-04-29 13:27 ` Avi Kivity
2012-04-30 7:45 ` Raghavendra K T
2012-04-30 7:45 ` Raghavendra K T
2012-04-23 10:00 ` Raghavendra K T
2012-04-23 10:00 ` [PATCH RFC V6 3/5] kvm guest : Add configuration support to enable debug information for KVM Guests Raghavendra K T
2012-04-23 10:00 ` Raghavendra K T
2012-04-23 10:00 ` [PATCH RFC V6 4/5] kvm : pv-ticketlocks support for linux guests running on KVM hypervisor Raghavendra K T
2012-04-23 10:00 ` Raghavendra K T
2012-04-23 10:00 ` Raghavendra K T
2012-04-23 10:00 ` [PATCH RFC V6 5/5] Documentation/kvm : Add documentation on Hypercalls and features used for PV spinlock Raghavendra K T
2012-04-23 10:00 ` Raghavendra K T
2012-04-26 15:57 ` Rob Landley
2012-04-26 16:04 ` Raghavendra K T
2012-04-26 16:04 ` Raghavendra K T
2012-04-26 15:57 ` Rob Landley
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=4F9D417D.1050105@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vatsa@linux.vnet.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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.