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]
Message-ID: <4F0C0EBB.3090506@tu-ilmenau.de>
Date:	Tue, 10 Jan 2012 11:11:07 +0100
From:	Stephan Bärwolf <stephan.baerwolf@...ilmenau.de>
To:	Avi Kivity <avi@...hat.com>
CC:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: KVM guest-kernel panics double fault

Hello.

Thank you for your lots of information, they helped very much -
especially debugging...

> The third parameter is actually ecx
(ebx was actually a typing...  ...of course ecx!)

> The emulator is written to be independent of the rest of kvm, using
> emul_to_vcpu() undoes that.  If you need access to more vpcu internals,
> add more function pointers to struct x86_emulate_ops.
I prepare/adapt everything to the mentioned styles/policy.
(I'll insert 2 additional ops for getting "cpuid" and "id of vcpu"...)


> Please post patches separately, not as attachments to a single email. 
> See Documentation/SubmittingPatches.
One thing, which is not fully clear to me: Where exactly should I post
the patches?
Also to/in this mail/group as an empty mail (containing the patch as
text-body) per patch?
Or all (3 patches) at once?
Do you prefer them in a git-repo for example at github?

Again, thank you a lot

regards Stephan

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ