qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: stefano.stabellini@eu.citrix.com, Ian.Jackson@eu.citrix.com,
	qemu-devel@nongnu.org, kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem
Date: Fri, 19 Dec 2008 14:51:57 -0600	[thread overview]
Message-ID: <494C096D.1050902@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580812191157n3b56d7b6hf6d0e049a64898e@mail.gmail.com>

Blue Swirl wrote:
> On 12/18/08, Glauber Costa <glommer@redhat.com> wrote:
>   
>> Since now we have our own memory read/write function, we don't
>>  depend on all of tcg data structures anymore. So, instead of filling
>>  them up, bypass it altogether by using kvm_set_phys mem alone.
>>
>>  To do that, we now have to provide our own way to get page
>>  information given the address. (kvm_get_physical_page_desc)
>>
>>  Signed-off-by: Glauber Costa <glommer@redhat.com>
>>     
>
>   
>>  +static void tcg_register_physical_memory_offset(target_phys_addr_t start_addr,
>>     
>
> I don't think TCG actually has much to do with the function.

It really does though.  The way physical memory is registered and 
managed is TCG specific right now.  It has deep hooks for invalidating 
TranslationBlock's, and the table structure is designed to be conducive 
to the access patterns of TCG.

If you think of a higher level CPU API, I think registering physical 
memory and reading/writing physical memory would end up being part of 
that API.

Regards,

Anthony Liguori

>  Would
> no_kvm be too ugly?
>
> More philosophically, what is (Qemu /\ ~KVM /\ ~TCG)? I hope I got the
> math right.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   

  parent reply	other threads:[~2008-12-19 20:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 17:01 [Qemu-devel] [PATCH 0/6] bypass tcg memory functions -v2 Glauber Costa
2008-12-18 17:01 ` [Qemu-devel] [PATCH 1/6] remove smaller slots if registering a bigger one Glauber Costa
2008-12-18 17:01   ` [Qemu-devel] [PATCH 2/6] re-register whole area upon lfb unmap Glauber Costa
2008-12-18 17:01     ` [Qemu-devel] [PATCH 3/6] isolate io handling routine Glauber Costa
2008-12-18 17:01       ` [Qemu-devel] [PATCH 4/6] replace cpu_physical_memory_rw Glauber Costa
2008-12-18 17:01         ` [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem Glauber Costa
2008-12-18 17:01           ` [Qemu-devel] [PATCH 6/6] cache slot lookup Glauber Costa
2008-12-19 19:57           ` [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem Blue Swirl
2008-12-19 20:14             ` Laurent Desnogues
2008-12-19 20:51             ` Anthony Liguori [this message]
2008-12-20 11:28               ` Blue Swirl
2008-12-22 17:00                 ` Glauber Costa
2008-12-23 11:43                   ` Blue Swirl
  -- strict thread matches above, loose matches on Subject: below --
2009-01-20 18:50 [Qemu-devel] [PATCH 0/6] Bypass tcg memory functions -v1.0-2009 Glauber Costa
2009-01-20 18:51 ` [Qemu-devel] [PATCH 1/6] remove smaller slots if registering a bigger one Glauber Costa
2009-01-20 18:51   ` [Qemu-devel] [PATCH 2/6] re-register whole area upon lfb unmap Glauber Costa
2009-01-20 18:51     ` [Qemu-devel] [PATCH 3/6] isolate io handling routine Glauber Costa
2009-01-20 18:51       ` [Qemu-devel] [PATCH 4/6] replace cpu_physical_memory_rw Glauber Costa
2009-01-20 18:51         ` [Qemu-devel] [PATCH 5/6] hook cpu_register_physical_mem Glauber Costa

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=494C096D.1050902@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).