From: Jan Kiszka <jan.kiszka@web.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>,
agraf@suse.de
Subject: Re: [Qemu-trivial] [PATCH] Permit -mem-path without sync mmu
Date: Fri, 05 Aug 2011 08:16:42 +0200 [thread overview]
Message-ID: <4E3B8ACA.7080104@web.de> (raw)
In-Reply-To: <1312516970-26606-1-git-send-email-david@gibson.dropbear.id.au>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
On 2011-08-05 06:02, David Gibson wrote:
> At present, an explicit test disallows use of -mem-path when kvm is enabled
> but KVM_CAP_SYNC_MMU is not set. In particular, this prevents the user
> from using hugetlbfs to back the guest memory.
>
> I can see no reason for this check, and when I asked about it previously,
> the only theory offered was that this was a limitation of the very early
> days of kvm which only happened to match the SYNC_MMU flag by accident.
>
> This patch, therefore, removes the check. This is of particular use to
> us on POWER, where we haven't yet implement SYNC_MMU, but where backing
> the guest with hugepages is possible, and in fact mandatory (for now).
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> exec.c | 5 -----
> 1 files changed, 0 insertions(+), 5 deletions(-)
>
> diff --git a/exec.c b/exec.c
> index 476b507..041637c 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -2818,11 +2818,6 @@ static void *file_ram_alloc(RAMBlock *block,
> return NULL;
> }
>
> - if (kvm_enabled() && !kvm_has_sync_mmu()) {
> - fprintf(stderr, "host lacks kvm mmu notifiers, -mem-path unsupported\n");
> - return NULL;
> - }
> -
> if (asprintf(&filename, "%s/qemu_back_mem.XXXXXX", path) == -1) {
> return NULL;
> }
This is nothing trivial, see ce9a92411d in qemu-kvm or
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/27380. And it
should rather target uq/master. CCing Avi, Marcelo, and the kvm list.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>,
agraf@suse.de
Subject: Re: [PATCH] Permit -mem-path without sync mmu
Date: Fri, 05 Aug 2011 08:16:42 +0200 [thread overview]
Message-ID: <4E3B8ACA.7080104@web.de> (raw)
In-Reply-To: <1312516970-26606-1-git-send-email-david@gibson.dropbear.id.au>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
On 2011-08-05 06:02, David Gibson wrote:
> At present, an explicit test disallows use of -mem-path when kvm is enabled
> but KVM_CAP_SYNC_MMU is not set. In particular, this prevents the user
> from using hugetlbfs to back the guest memory.
>
> I can see no reason for this check, and when I asked about it previously,
> the only theory offered was that this was a limitation of the very early
> days of kvm which only happened to match the SYNC_MMU flag by accident.
>
> This patch, therefore, removes the check. This is of particular use to
> us on POWER, where we haven't yet implement SYNC_MMU, but where backing
> the guest with hugepages is possible, and in fact mandatory (for now).
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> exec.c | 5 -----
> 1 files changed, 0 insertions(+), 5 deletions(-)
>
> diff --git a/exec.c b/exec.c
> index 476b507..041637c 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -2818,11 +2818,6 @@ static void *file_ram_alloc(RAMBlock *block,
> return NULL;
> }
>
> - if (kvm_enabled() && !kvm_has_sync_mmu()) {
> - fprintf(stderr, "host lacks kvm mmu notifiers, -mem-path unsupported\n");
> - return NULL;
> - }
> -
> if (asprintf(&filename, "%s/qemu_back_mem.XXXXXX", path) == -1) {
> return NULL;
> }
This is nothing trivial, see ce9a92411d in qemu-kvm or
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/27380. And it
should rather target uq/master. CCing Avi, Marcelo, and the kvm list.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>,
agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH] Permit -mem-path without sync mmu
Date: Fri, 05 Aug 2011 08:16:42 +0200 [thread overview]
Message-ID: <4E3B8ACA.7080104@web.de> (raw)
In-Reply-To: <1312516970-26606-1-git-send-email-david@gibson.dropbear.id.au>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
On 2011-08-05 06:02, David Gibson wrote:
> At present, an explicit test disallows use of -mem-path when kvm is enabled
> but KVM_CAP_SYNC_MMU is not set. In particular, this prevents the user
> from using hugetlbfs to back the guest memory.
>
> I can see no reason for this check, and when I asked about it previously,
> the only theory offered was that this was a limitation of the very early
> days of kvm which only happened to match the SYNC_MMU flag by accident.
>
> This patch, therefore, removes the check. This is of particular use to
> us on POWER, where we haven't yet implement SYNC_MMU, but where backing
> the guest with hugepages is possible, and in fact mandatory (for now).
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> exec.c | 5 -----
> 1 files changed, 0 insertions(+), 5 deletions(-)
>
> diff --git a/exec.c b/exec.c
> index 476b507..041637c 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -2818,11 +2818,6 @@ static void *file_ram_alloc(RAMBlock *block,
> return NULL;
> }
>
> - if (kvm_enabled() && !kvm_has_sync_mmu()) {
> - fprintf(stderr, "host lacks kvm mmu notifiers, -mem-path unsupported\n");
> - return NULL;
> - }
> -
> if (asprintf(&filename, "%s/qemu_back_mem.XXXXXX", path) == -1) {
> return NULL;
> }
This is nothing trivial, see ce9a92411d in qemu-kvm or
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/27380. And it
should rather target uq/master. CCing Avi, Marcelo, and the kvm list.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-08-06 13:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 4:02 [Qemu-trivial] [PATCH] Permit -mem-path without sync mmu David Gibson
2011-08-05 4:02 ` [Qemu-devel] " David Gibson
2011-08-05 6:16 ` Jan Kiszka [this message]
2011-08-05 6:16 ` Jan Kiszka
2011-08-05 6:16 ` Jan Kiszka
2011-08-05 15:30 ` Marcelo Tosatti
2011-08-05 15:30 ` [Qemu-devel] " Marcelo Tosatti
2011-08-08 6:03 ` David Gibson
2011-08-08 6:03 ` [Qemu-devel] " David Gibson
2011-08-08 8:24 ` Avi Kivity
2011-08-08 8:24 ` [Qemu-devel] " Avi Kivity
2011-08-10 5:10 ` David Gibson
2011-08-10 5:10 ` [Qemu-devel] " David Gibson
2011-08-10 9:01 ` Avi Kivity
2011-08-11 6:09 ` David Gibson
2011-08-11 6:09 ` David Gibson
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=4E3B8ACA.7080104@web.de \
--to=jan.kiszka@web.de \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.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.