From: Dave Hansen <dave@linux.vnet.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Gleb Natapov <gleb@redhat.com>,
x86@kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 5/5] fix kvm's use of __pa() on percpu areas
Date: Mon, 21 Jan 2013 10:59:40 -0800 [thread overview]
Message-ID: <50FD901C.8000002@linux.vnet.ibm.com> (raw)
In-Reply-To: <08cba1bf-6476-4fad-8d29-e380ec7127ba@email.android.com>
On 01/21/2013 10:38 AM, H. Peter Anvin wrote:
> Final question: are any of these done in frequent paths? (I believe no, but...)
Nope. All of the places that it gets used here are in
initialization-time paths. The two we have here are when kvm and the
host are setting up a new vcpu and when the kvmclock clocksource is
being registered. A CPU getting hotplugged is the only thing that might
even have these get called more than at boot.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Gleb Natapov <gleb@redhat.com>,
x86@kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 5/5] fix kvm's use of __pa() on percpu areas
Date: Mon, 21 Jan 2013 10:59:40 -0800 [thread overview]
Message-ID: <50FD901C.8000002@linux.vnet.ibm.com> (raw)
In-Reply-To: <08cba1bf-6476-4fad-8d29-e380ec7127ba@email.android.com>
On 01/21/2013 10:38 AM, H. Peter Anvin wrote:
> Final question: are any of these done in frequent paths? (I believe no, but...)
Nope. All of the places that it gets used here are in
initialization-time paths. The two we have here are when kvm and the
host are setting up a new vcpu and when the kvmclock clocksource is
being registered. A CPU getting hotplugged is the only thing that might
even have these get called more than at boot.
next prev parent reply other threads:[~2013-01-21 18:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 17:52 [PATCH 0/5] fix illegal use of __pa() in KVM code Dave Hansen
2013-01-21 17:52 ` Dave Hansen
2013-01-21 17:52 ` [PATCH 1/5] make DEBUG_VIRTUAL work earlier in boot Dave Hansen
2013-01-21 17:52 ` Dave Hansen
2013-01-21 17:52 ` [PATCH 2/5] pagetable level size/shift/mask helpers Dave Hansen
2013-01-21 17:52 ` Dave Hansen
2013-01-21 17:52 ` [PATCH 3/5] use new pagetable helpers in try_preserve_large_page() Dave Hansen
2013-01-21 17:52 ` Dave Hansen
2013-01-21 17:52 ` [PATCH 4/5] create slow_virt_to_phys() Dave Hansen
2013-01-21 17:52 ` Dave Hansen
2013-01-21 18:08 ` H. Peter Anvin
2013-01-21 18:08 ` H. Peter Anvin
2013-01-21 18:18 ` Dave Hansen
2013-01-21 18:18 ` Dave Hansen
2013-01-21 17:52 ` [PATCH 5/5] fix kvm's use of __pa() on percpu areas Dave Hansen
2013-01-21 17:52 ` Dave Hansen
2013-01-21 18:38 ` H. Peter Anvin
2013-01-21 18:38 ` H. Peter Anvin
2013-01-21 18:59 ` Dave Hansen [this message]
2013-01-21 18:59 ` Dave Hansen
2013-01-21 19:22 ` H. Peter Anvin
2013-01-21 19:22 ` H. Peter Anvin
2013-01-21 19:02 ` Gleb Natapov
2013-01-21 19:02 ` Gleb Natapov
-- strict thread matches above, loose matches on Subject: below --
2013-01-22 21:24 [PATCH 0/5] [v3] fix illegal use of __pa() in KVM code Dave Hansen
2013-01-22 21:24 ` [PATCH 5/5] fix kvm's use of __pa() on percpu areas Dave Hansen
2013-01-22 21:24 ` Dave Hansen
2013-01-23 0:08 ` Marcelo Tosatti
2013-01-23 0:08 ` Marcelo Tosatti
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=50FD901C.8000002@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtosatti@redhat.com \
--cc=riel@redhat.com \
--cc=x86@kernel.org \
/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.