public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
	Hollis Blanchard
	<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] Use a table to dispatch IO requests in kvmctl
Date: Wed, 10 Oct 2007 08:42:43 -0500	[thread overview]
Message-ID: <470CD6D3.8080805@us.ibm.com> (raw)
In-Reply-To: <470CD2CD.5090903-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Avi Kivity wrote:
> Anthony Liguori wrote:
>> Avi Kivity wrote:
>>> Anthony Liguori wrote:
>>>  
>>>> This patch attempts to clean up kvmctl so that it can be more 
>>>> easily made to
>>>> work for multiple architectures and to support more emulation.
>>>>
>>>> It introduces a io dispatch mechanism.  This mechanism supports 
>>>> subpage
>>>> granularity but is optimized to efficiently cover regions of pages 
>>>> too.  It's
>>>> a 64-bit address space that's structured as a 5-level table.
>>>>       
>>>
>>>
>>> Why not use a simple array?
>>>   
>>
>> For MMIO too?
>
> Yes.
>
>>
>> QEMU uses an array for PIO but a table for MMIO.  I figured it would 
>> be best to just use the same table.
>
> Or the same array?

Indexed by the address or just sorted and searchable?  MMIO addresses 
are rather sparse so the former seems like the only sane thing.  It also 
has to support subpage granularity.

Regards,

Anthony Liguori


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-10-10 13:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 21:40 [PATCH] Use a table to dispatch IO requests in kvmctl Anthony Liguori
     [not found] ` <11919660094186-git-send-email-aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-10-09 22:10   ` Anthony Liguori
2007-10-10  6:46   ` Hollis Blanchard
2007-10-10  7:14   ` Avi Kivity
     [not found]     ` <470C7BDC.7020106-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-10 13:24       ` Anthony Liguori
     [not found]         ` <470CD298.8060704-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-10-10 13:25           ` Avi Kivity
     [not found]             ` <470CD2CD.5090903-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-10 13:42               ` Anthony Liguori [this message]
     [not found]                 ` <470CD6D3.8080805-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-10-10 13:47                   ` Avi Kivity
     [not found]                     ` <470CD7EA.3040500-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-10 13:59                       ` Anthony Liguori

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=470CD6D3.8080805@us.ibm.com \
    --to=aliguori-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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