netdev - Re: [PATCH v3 3/6] vbus: add a "vbus-proxy" bus model

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:	Tue, 18 Aug 2009 15:38:30 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Gregory Haskins <GHaskins@...ell.com>
CC:	mingo@...e.hu, gregory.haskins@...il.com,
	alacrityvm-devel@...ts.sourceforge.net, mst@...hat.com,
	kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH v3 3/6] vbus: add a "vbus-proxy" bus model

On 08/18/2009 03:36 PM, Gregory Haskins wrote:
> Yeah, I agree.  I am not advocating we expend energy on this now.  But my thoughts at the time were that that particular problem can be solved at io-setup time with some kind of call to qualify the address.
>
> Iow: a slow path call with the address would return flags on whether iowrite() should do a real io, or a IOoHC.
>    

Yes, it could work, though we'd need somewhere to stow this 
information.  IIRC Arnd suggested a bit from the address itself.

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

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html