| 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: Mon, 12 Dec 2011 12:59:52 +0200 From: Sasha Levin <levinsasha928@...il.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>, Pekka Enberg <penberg@...nel.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [patch 0/3] kvm tool: Serial emulation overhaul On Mon, 2011-12-12 at 10:27 +0000, Alan Cox wrote: > > Well, the difference between ssh and serial is, that ssh can pack 1.5k > > worth of data into one frame, while serial has to send it > > piecewise. And the emulation has to trap into kvm tool for each tx > > byte, which doesnt help either. We cannot do much with buffering on > > the kvm tool side as we have no clue how much consecutive data will > > come in. That's why there is a virtual console, which has the > > disadvantage that you cant see the early boot messages. > > You can emulate a chip with a 64byte or so FIFO. You can do I/O cycle > prediction in the kernel part and you can use the empty bit as a clue > (which is what most serial<->ethernet widgetry does). The performance problems here aren't the same performance problems you have on real hardware. The problem here is that it costs 40k cycles for the guest to access the emulated chip. -- Sasha. -- 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