| 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
| ||
|
Date: Wed, 10 Nov 2010 11:47:56 -0600 From: Anthony Liguori <anthony@...emonkey.ws> To: Ian Molton <ian.molton@...labora.co.uk> CC: QEMU Developers <qemu-devel@...gnu.org>, Rusty Russell <rusty@...tcorp.com.au>, linux-kernel@...r.kernel.org, virtualization@...ts.linux-foundation.org, virtualization@...ts.osdl.org, Alon Levy <alevy@...hat.com>, Avi Kivity <avi@...hat.com> Subject: Re: [Qemu-devel] Re: [PATCH] Implement a virtio GPU transport On 11/10/2010 11:22 AM, Ian Molton wrote: > Ping ? I think the best way forward is to post patches. To summarize what I was trying to express in the thread, I think this is not the right long term architecture but am not opposed to it as a short term solution. I think having a new virtio device is a bad design choice but am not totally opposed to it. My advice is that using virtio-serial + an external tool is probably the least amount of work to get something working and usable with QEMU. If you want to go for the path of integration, you're going to have to fix all of the coding style issues and make the code fit into QEMU. Dropping a bunch of junk into target-i386/ is not making the code fit into QEMU. If you post just what you have now in patch form, I can try to provide more concrete advice ignoring the coding style problems. Regards, Anthony Liguori -- 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/
Powered by blists - more mailing lists