linux-kernel - Re: [PATCH v2 3/4] KVM: add io services to xinterface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 04 Oct 2009 12:26:25 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Gregory Haskins <ghaskins@...ell.com>
CC:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/4] KVM: add io services to xinterface

On 10/02/2009 10:19 PM, Gregory Haskins wrote:
> We want to add a more efficient way to get PIO signals out of the guest,
> so we add an "xioevent" interface.  This allows a client to register
> for notifications when a specific MMIO/PIO address is touched by
> the guest.  This is an alternative interface to ioeventfd, which is
> performance limited by io-bus scaling and eventfd wait-queue based
> notification mechanism.  This also has the advantage of retaining
> the full PIO data payload and passing it to the recipient.
>
>    

Can you detail the problems with io-bus scaling and eventfd 
wait-queues?  Maybe we should fix these instead.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/