public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/5] kvm: Batch writes to MMIO
Date: Wed, 04 Jun 2008 18:13:23 +0300	[thread overview]
Message-ID: <4846B113.4030904@qumranet.com> (raw)
In-Reply-To: <1212156357946-git-send-email-Laurent.Vivier@bull.net>

Laurent Vivier wrote:
> When kernel has to send MMIO writes to userspace, it stores them
> in memory until it has to pass the hand to userspace for another
> reason. This avoids to have too many context switches on operations
> that can wait.
>
> These patches introduce an ioctl() to define MMIO allowed to be coalesced.
>
> This is the kernel part of the coalesced MMIO functionality.
>
>   

Applied all, thanks.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  parent reply	other threads:[~2008-06-04 15:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 14:05 [PATCH 0/5] kvm: Batch writes to MMIO Laurent Vivier
2008-05-30 14:05 ` [PATCH 1/5] kvm_io_device: extend in_range() to manage len and write attribute Laurent Vivier
2008-05-30 14:05   ` [PATCH 2/5] Add coalesced MMIO support (common part) Laurent Vivier
2008-05-30 14:05     ` [PATCH 3/5] Add coalesced MMIO support (x86 part) Laurent Vivier
2008-05-30 14:05       ` [PATCH 4/5] Add coalesced MMIO support (powerpc part) Laurent Vivier
2008-05-30 14:05         ` [PATCH 5/5] Add coalesced MMIO support (ia64 part) Laurent Vivier
2008-06-04 15:13 ` Avi Kivity [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-23  8:50 [PATCH 0/5] kvm: Batch writes to MMIO Laurent Vivier
2008-05-26 12:00 ` Avi Kivity
2008-05-26 12:10   ` Laurent Vivier
2008-05-26 13:43     ` Avi Kivity
2008-05-26 14:20 ` 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=4846B113.4030904@qumranet.com \
    --to=avi@qumranet.com \
    --cc=Laurent.Vivier@bull.net \
    --cc=kvm@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