From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping
Date: Mon, 04 May 2009 08:59:25 +0000 [thread overview]
Message-ID: <49FEAE6D.9040708@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC236A2BC03@pdsmsx503.ccr.corp.intel.com>
Avi Kivity wrote:
> Jes Sorensen wrote:
>> Avi Kivity wrote:
>>> Hollis, does this work for you?
>>>
>>> If now, you can add a new define KVM_WANT_MAPPING or something, and
>>> define it for I386 and IA64.
>>
>>
>> Hi,
>>
>> This is the one implementing the KVM_WANT_MAPPING change.
>>
>> Cheers,
>> Jes
>>
>>
>
> There is in fact a call to drop_mapping() outside any #ifdef (in
> kvm_cpu_register_physical_memory()). I'm confused... maybe we should
> make this code unconditional.
>
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: "Zhang, Xiantao" <xiantao.zhang@intel.com>,
Hollis Blanchard <hollisb@us.ibm.com>,
"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
kvm-devel <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping
Date: Mon, 04 May 2009 08:59:25 +0000 [thread overview]
Message-ID: <49FEAE6D.9040708@redhat.com> (raw)
In-Reply-To: <49FEAE3A.2070001@redhat.com>
Avi Kivity wrote:
> Jes Sorensen wrote:
>> Avi Kivity wrote:
>>> Hollis, does this work for you?
>>>
>>> If now, you can add a new define KVM_WANT_MAPPING or something, and
>>> define it for I386 and IA64.
>>
>>
>> Hi,
>>
>> This is the one implementing the KVM_WANT_MAPPING change.
>>
>> Cheers,
>> Jes
>>
>>
>
> There is in fact a call to drop_mapping() outside any #ifdef (in
> kvm_cpu_register_physical_memory()). I'm confused... maybe we should
> make this code unconditional.
>
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: "Zhang, Xiantao" <xiantao.zhang@intel.com>,
Hollis Blanchard <hollisb@us.ibm.com>,
"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
kvm-devel <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also.
Date: Mon, 04 May 2009 11:59:25 +0300 [thread overview]
Message-ID: <49FEAE6D.9040708@redhat.com> (raw)
In-Reply-To: <49FEAE3A.2070001@redhat.com>
Avi Kivity wrote:
> Jes Sorensen wrote:
>> Avi Kivity wrote:
>>> Hollis, does this work for you?
>>>
>>> If now, you can add a new define KVM_WANT_MAPPING or something, and
>>> define it for I386 and IA64.
>>
>>
>> Hi,
>>
>> This is the one implementing the KVM_WANT_MAPPING change.
>>
>> Cheers,
>> Jes
>>
>>
>
> There is in fact a call to drop_mapping() outside any #ifdef (in
> kvm_cpu_register_physical_memory()). I'm confused... maybe we should
> make this code unconditional.
>
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-05-04 8:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 9:29 [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Zhang, Xiantao
2009-04-28 9:29 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Zhang, Xiantao
2009-04-28 9:39 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Avi Kivity
2009-04-28 9:39 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Avi Kivity
2009-04-28 9:39 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Avi Kivity
2009-04-29 14:59 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Jes Sorensen
2009-04-29 14:59 ` Jes Sorensen
2009-04-29 14:59 ` Jes Sorensen
2009-04-29 15:04 ` Re: [PATCH 04/04] qemu-kvm: other archs should maintain memory Jes Sorensen
2009-04-29 15:04 ` Re: [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Jes Sorensen
2009-04-29 15:04 ` Re: [PATCH 04/04] qemu-kvm: other archs should maintain memory Jes Sorensen
2009-04-29 15:06 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Jes Sorensen
2009-04-29 15:06 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Jes Sorensen
2009-04-29 15:06 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Jes Sorensen
2009-05-04 8:51 ` Avi Kivity
2009-05-04 8:51 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Avi Kivity
2009-05-04 8:51 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Avi Kivity
2009-05-04 8:59 ` Avi Kivity [this message]
2009-05-04 8:59 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Avi Kivity
2009-05-04 8:59 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Avi Kivity
2009-05-04 9:17 ` Jes Sorensen
2009-05-04 9:17 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Jes Sorensen
2009-05-04 9:17 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Jes Sorensen
2009-05-04 9:25 ` Jes Sorensen
2009-05-04 9:25 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Jes Sorensen
2009-05-04 9:25 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Jes Sorensen
2009-05-04 21:57 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory Hollis Blanchard
2009-05-04 21:57 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mappingalso Hollis Blanchard
2009-05-04 21:57 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory Hollis Blanchard
2009-05-11 10:15 ` Zhang, Xiantao
2009-05-11 10:15 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Zhang, Xiantao
2009-05-11 11:18 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping Jes Sorensen
2009-05-11 11:18 ` [PATCH 04/04] qemu-kvm: other archs should maintain memory mapping also Jes Sorensen
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=49FEAE6D.9040708@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.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.