From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <longman@redhat.com>
Cc: linux-arch@vger.kernel.org, "Juergen Gross" <jgross@suse.com>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
x86@kernel.org, kvm@vger.kernel.org,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Pan Xinhui" <xinhui.pan@linux.vnet.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
"Chris Wright" <chrisw@sous-sol.org>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org,
"Alok Kataria" <akataria@vmware.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH v2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function
Date: Tue, 14 Feb 2017 10:39:46 +0100 [thread overview]
Message-ID: <20170214093946.GM6500__19707.577818963$1487065254$gmane$org@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <933ba8c6-4ebe-63e2-3c3a-2e5afef9269a@redhat.com>
On Mon, Feb 13, 2017 at 05:34:01PM -0500, Waiman Long wrote:
> It is the address of &steal_time that will exceed the 32-bit limit.
That seems extremely unlikely. That would mean we have more than 4G
worth of per-cpu variables declared in the kernel.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-14 9:40 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 15:43 [PATCH v2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function Waiman Long
2017-02-10 15:43 ` Waiman Long
2017-02-10 16:19 ` Peter Zijlstra
2017-02-10 16:19 ` Peter Zijlstra
2017-02-10 16:19 ` Peter Zijlstra
2017-02-10 16:35 ` Waiman Long
2017-02-10 16:35 ` Waiman Long
2017-02-10 17:00 ` Waiman Long
2017-02-10 17:00 ` Waiman Long
2017-02-10 17:00 ` Waiman Long
2017-02-13 10:47 ` Peter Zijlstra
2017-02-13 10:47 ` Peter Zijlstra
2017-02-13 10:47 ` Peter Zijlstra
2017-02-13 10:53 ` Peter Zijlstra
2017-02-13 10:53 ` Peter Zijlstra
2017-02-13 10:53 ` Peter Zijlstra
2017-02-13 19:42 ` Waiman Long
2017-02-13 19:42 ` Waiman Long
2017-02-13 19:42 ` Waiman Long
2017-02-13 20:12 ` Waiman Long
2017-02-13 20:12 ` Waiman Long
2017-02-13 21:52 ` Peter Zijlstra
2017-02-13 21:52 ` Peter Zijlstra
2017-02-13 21:52 ` Peter Zijlstra
2017-02-13 22:00 ` hpa
2017-02-13 22:00 ` hpa
2017-02-13 22:00 ` hpa
2017-02-13 22:07 ` hpa
2017-02-13 22:07 ` hpa
2017-02-13 22:07 ` hpa
2017-02-13 22:34 ` Waiman Long
2017-02-13 22:34 ` Waiman Long
2017-02-13 22:34 ` Waiman Long
2017-02-13 22:36 ` hpa
2017-02-13 22:36 ` hpa
2017-02-13 22:36 ` hpa
2017-02-14 9:39 ` Peter Zijlstra [this message]
2017-02-14 9:39 ` Peter Zijlstra
2017-02-14 9:39 ` Peter Zijlstra
2017-02-14 14:46 ` Waiman Long
2017-02-14 14:46 ` Waiman Long
2017-02-14 14:46 ` Waiman Long
2017-02-14 16:03 ` Peter Zijlstra
2017-02-14 16:03 ` Peter Zijlstra
2017-02-14 16:03 ` Peter Zijlstra
2017-02-14 16:18 ` [Xen-devel] " Andrew Cooper
2017-02-14 16:18 ` Andrew Cooper
2017-02-14 16:18 ` [Xen-devel] " Andrew Cooper
2017-02-13 20:12 ` Waiman Long
2017-02-13 20:06 ` hpa
2017-02-13 20:06 ` hpa
2017-02-13 21:57 ` Peter Zijlstra
2017-02-13 21:57 ` Peter Zijlstra
2017-02-13 21:57 ` Peter Zijlstra
2017-02-13 22:24 ` Waiman Long
2017-02-13 22:24 ` Waiman Long
2017-02-13 22:31 ` Peter Zijlstra
2017-02-13 22:31 ` Peter Zijlstra
2017-02-13 22:31 ` Peter Zijlstra
2017-02-13 22:24 ` Waiman Long
2017-02-13 20:06 ` hpa
2017-02-13 19:41 ` Waiman Long
2017-02-13 19:41 ` Waiman Long
2017-02-13 19:41 ` Waiman Long
2017-02-10 16:35 ` Waiman Long
2017-02-10 16:22 ` Paolo Bonzini
2017-02-10 16:22 ` Paolo Bonzini
2017-02-10 16:22 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2017-02-10 15:43 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='20170214093946.GM6500__19707.577818963$1487065254$gmane$org@twins.programming.kicks-ass.net' \
--to=peterz@infradead.org \
--cc=akataria@vmware.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chrisw@sous-sol.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@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.