From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base
Date: Tue, 28 Apr 2009 12:49:25 +0000 [thread overview]
Message-ID: <49F6FB55.3000503@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC236A2BC04@pdsmsx503.ccr.corp.intel.com>
Jes Sorensen wrote:
>>>>>> "Avi" = Avi Kivity <avi@redhat.com> writes:
>>>>>>
>
> Avi> Zhang, Xiantao wrote:
>
>>>> qemu_get_ram_ptr() returns a pointer. Don't cast it to a
>>>> ram_addr_t, leave it a pointer.
>>>>
>>>> But why not use cpu_physical_memory_write() (or
>>>> cpu_physical_memory_write_rom())? It's much simpler and cleaner.
>>>>
>>>>
>>> Good suggestion! I just followed the original logic. Updated the
>>> patch. Xiantao
>>>
>
> Avi> Thanks, applied.
>
> Hi,
>
> I am not crazy about this patch. You need to use cpy_physical_memory_rw()
> in the hob and nvram code too, not just in the ipf.c code.
>
> What about the flush_icache_range() call you removed - is it safe to
> just discard that?
>
> I was in the process of working through this myself, but I am not
> quite finished. If you don't mind waiting a couple hours, I should
> have something a fair bit simpler to solve the same problem.
>
> Biggest issue is the flush_icache_range() one.
>
>
I haven't pushed this out yet, so I can apply a replacement patch.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-04-28 12:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 9:29 [PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base for Zhang, Xiantao
2009-04-28 9:49 ` [PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base Avi Kivity
2009-04-28 10:36 ` Zhang, Xiantao
2009-04-28 11:05 ` Avi Kivity
2009-04-28 12:38 ` [PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base for ipf.c Jes Sorensen
2009-04-28 12:49 ` Avi Kivity [this message]
2009-04-28 15:02 ` [PATCH 03/04] qemu-kvm: Remove the dependency for phys_ram_base Jes Sorensen
2009-04-29 2:04 ` Zhang, Xiantao
2009-04-29 2:05 ` Zhang, Xiantao
2009-04-29 8:21 ` Jes Sorensen
2009-04-29 8:35 ` Zhang, Xiantao
2009-04-29 8:42 ` Jes Sorensen
2009-04-29 14:02 ` Zhang, Xiantao
2009-04-29 15:07 ` Jes Sorensen
2009-04-30 9:11 ` Jes Sorensen
2009-04-30 9:23 ` Avi Kivity
2009-04-30 14:09 ` Jes Sorensen
2009-04-30 15:22 ` Avi Kivity
2009-05-01 10:30 ` Jes Sorensen
2009-05-03 16:14 ` Avi Kivity
2009-05-04 1:44 ` Zhang, Xiantao
2009-05-04 5:11 ` Jes Sorensen
2009-05-04 5:12 ` Zhang, Xiantao
2009-05-04 8:16 ` Avi Kivity
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=49F6FB55.3000503@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox