public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Anthony Liguori <aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
	Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] Use a table to dispatch IO requests in kvmctl
Date: Tue, 09 Oct 2007 23:46:15 -0700	[thread overview]
Message-ID: <1191998775.16235.44.camel@basalt> (raw)
In-Reply-To: <11919660094186-git-send-email-aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

On Tue, 2007-10-09 at 16:40 -0500, 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.

> For x86, we'll have two tables, a pio_table and an mmio_table.  For PPC we can
> just have a single table.  The IO functions can support accesses of up to 8
> bytes and can handle input/output in the same function.
> 
> I tried to keep this nice and simple so as to not add too much complexity to
> kvmctl.

I'm having a hard time seeing how this range stuff is useful.

Other than that, a 5-level table sounds like overcomplicating something
where a plain old hash table would do just fine, but it's only one
function so I guess I can't complain much.

-- 
Hollis Blanchard
IBM Linux Technology Center


-------------------------------------------------------------------------
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  6:46 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 [this message]
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
     [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=1191998775.16235.44.camel@basalt \
    --to=hollisb-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@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