From: Peter Zijlstra <peterz@infradead.org>
To: Juergen Gross <jgross@suse.com>
Cc: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
virtualization@lists.linux-foundation.org,
linux-s390@vger.kernel.org, mingo@redhat.com, mpe@ellerman.id.au,
paulus@samba.org, benh@kernel.crashing.org,
paulmck@linux.vnet.ibm.com, waiman.long@hpe.com,
will.deacon@arm.com, boqun.feng@gmail.com, dave@stgolabs.net,
schwidefsky@de.ibm.com, pbonzini@redhat.com,
xen-devel-request@lists.xenproject.org
Subject: Re: [PATCH v2 0/4] implement vcpu preempted check
Date: Wed, 6 Jul 2016 10:19:20 +0200 [thread overview]
Message-ID: <20160706081920.GG30921@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <577CB786.8000902@suse.com>
On Wed, Jul 06, 2016 at 09:47:18AM +0200, Juergen Gross wrote:
> On 06/07/16 08:52, Peter Zijlstra wrote:
> > Paolo, could you help out with an (x86) KVM interface for this?
>
> Xen support of this interface should be rather easy. Could you please
> Cc: xen-devel-request@lists.xenproject.org in the next version?
So meta question; aren't all you virt people looking at the regular
virtualization list? Or should we really dig out all the various
hypervisor lists and Cc them?
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Juergen Gross <jgross@suse.com>
Cc: linux-s390@vger.kernel.org,
xen-devel-request@lists.xenproject.org, dave@stgolabs.net,
benh@kernel.crashing.org,
Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>,
boqun.feng@gmail.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, waiman.long@hpe.com,
virtualization@lists.linux-foundation.org, mingo@redhat.com,
paulus@samba.org, mpe@ellerman.id.au, schwidefsky@de.ibm.com,
pbonzini@redhat.com, paulmck@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 0/4] implement vcpu preempted check
Date: Wed, 6 Jul 2016 10:19:20 +0200 [thread overview]
Message-ID: <20160706081920.GG30921@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <577CB786.8000902@suse.com>
On Wed, Jul 06, 2016 at 09:47:18AM +0200, Juergen Gross wrote:
> On 06/07/16 08:52, Peter Zijlstra wrote:
> > Paolo, could you help out with an (x86) KVM interface for this?
>
> Xen support of this interface should be rather easy. Could you please
> Cc: xen-devel-request@lists.xenproject.org in the next version?
So meta question; aren't all you virt people looking at the regular
virtualization list? Or should we really dig out all the various
hypervisor lists and Cc them?
next prev parent reply other threads:[~2016-07-06 8:19 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 14:43 [PATCH v2 0/4] implement vcpu preempted check Pan Xinhui
2016-06-28 14:43 ` Pan Xinhui
2016-06-28 14:43 ` [PATCH v2 1/4] kernel/sched: introduce vcpu preempted check interface Pan Xinhui
2016-06-28 14:43 ` Pan Xinhui
2016-06-28 14:43 ` [PATCH v2 2/4] powerpc/spinlock: support vcpu preempted check Pan Xinhui
2016-06-28 14:43 ` Pan Xinhui
2016-07-05 9:57 ` Wanpeng Li
2016-07-05 9:57 ` Wanpeng Li
2016-07-06 4:58 ` xinhui
2016-07-06 4:58 ` xinhui
2016-07-06 6:46 ` Wanpeng Li
2016-07-06 6:46 ` Wanpeng Li
2016-07-06 6:46 ` Wanpeng Li
2016-07-06 7:58 ` Peter Zijlstra
2016-07-06 7:58 ` Peter Zijlstra
2016-07-06 8:32 ` Wanpeng Li
2016-07-06 8:32 ` Wanpeng Li
2016-07-06 10:18 ` xinhui
2016-07-06 10:18 ` xinhui
2016-07-06 10:54 ` Balbir Singh
2016-07-06 10:54 ` Balbir Singh
2016-07-06 10:54 ` Balbir Singh
2016-07-15 15:35 ` Pan Xinhui
2016-07-15 15:35 ` Pan Xinhui
2016-06-28 14:43 ` [PATCH v2 3/4] locking/osq: Drop the overload of osq_lock() Pan Xinhui
2016-06-28 14:43 ` Pan Xinhui
2016-06-28 14:43 ` [PATCH v2 4/4] kernel/locking: Drop the overload of {mutex,rwsem}_spin_on_owner Pan Xinhui
2016-06-28 14:43 ` [PATCH v2 4/4] kernel/locking: Drop the overload of {mutex, rwsem}_spin_on_owner Pan Xinhui
2016-06-28 14:43 ` Pan Xinhui
2016-07-06 6:52 ` [PATCH v2 0/4] implement vcpu preempted check Peter Zijlstra
2016-07-06 6:52 ` Peter Zijlstra
2016-07-06 7:47 ` Juergen Gross
2016-07-06 7:47 ` Juergen Gross
2016-07-06 8:19 ` Peter Zijlstra [this message]
2016-07-06 8:19 ` Peter Zijlstra
2016-07-06 8:38 ` Juergen Gross
2016-07-06 8:38 ` Juergen Gross
2016-07-06 12:44 ` Paolo Bonzini
2016-07-06 12:44 ` Paolo Bonzini
2016-07-06 16:56 ` Christian Borntraeger
2016-07-06 16:56 ` Christian Borntraeger
2016-07-06 16:56 ` Christian Borntraeger
2016-07-06 10:05 ` xinhui
2016-07-06 10:05 ` xinhui
2016-07-06 10:44 ` Paolo Bonzini
2016-07-06 11:59 ` Peter Zijlstra
2016-07-06 11:59 ` Peter Zijlstra
2016-07-06 12:08 ` Wanpeng Li
2016-07-06 12:08 ` Wanpeng Li
2016-07-06 12:28 ` Paolo Bonzini
2016-07-06 12:28 ` Paolo Bonzini
2016-07-06 13:03 ` Wanpeng Li
2016-07-06 13:03 ` Wanpeng Li
2016-07-07 8:48 ` Wanpeng Li
2016-07-07 8:48 ` Wanpeng Li
2016-07-07 9:42 ` Peter Zijlstra
2016-07-07 9:42 ` Peter Zijlstra
2016-07-07 10:12 ` Wanpeng Li
2016-07-07 10:12 ` Wanpeng Li
2016-07-07 10:27 ` Wanpeng Li
2016-07-07 10:27 ` Wanpeng Li
2016-07-07 11:15 ` Peter Zijlstra
2016-07-07 11:15 ` Peter Zijlstra
2016-07-07 11:08 ` Peter Zijlstra
2016-07-07 11:08 ` Peter Zijlstra
2016-07-07 11:09 ` Peter Zijlstra
2016-07-07 11:09 ` Peter Zijlstra
2016-07-07 11:21 ` Peter Zijlstra
2016-07-07 11:21 ` Peter Zijlstra
2016-07-11 15:10 ` Waiman Long
2016-07-11 15:10 ` Waiman Long
2016-07-11 15:10 ` Waiman Long
2016-07-12 4:16 ` Juergen Gross
2016-07-12 4:16 ` Juergen Gross
2016-07-12 18:16 ` Waiman Long
2016-07-12 18:16 ` Waiman Long
2016-07-12 18:16 ` Waiman Long
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=20160706081920.GG30921@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=waiman.long@hpe.com \
--cc=will.deacon@arm.com \
--cc=xen-devel-request@lists.xenproject.org \
--cc=xinhui.pan@linux.vnet.ibm.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.