From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [patch] KVM: fix hypercall cache/decache
Date: Tue, 20 Mar 2007 11:21:20 +0200 [thread overview]
Message-ID: <45FFA790.7080007@qumranet.com> (raw)
In-Reply-To: <20070320085427.GA21948-X9Un+BFzKDI@public.gmane.org>
Ingo Molnar wrote:
> Subject: [patch] KVM: fix hypercall cache/decache
> From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
>
> a recent change to kvm_hypercall() flipped around the order of
> ->cache_regs() and ->decache_regs(), but that is bogus and causes
> ESP/RIP corruption: ->cache_regs() will 'cache' the CPU-side registers
> into the vcpu structure, and ->decache_regs() will sync it back to the
> CPU.
>
> fix this by using the correct order again.
>
>
That's 57d78025d84fb607aa335d015a79b257517aa209 in my tree...
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-20 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 8:54 [patch] KVM: fix hypercall cache/decache Ingo Molnar
[not found] ` <20070320085427.GA21948-X9Un+BFzKDI@public.gmane.org>
2007-03-20 9:21 ` Avi Kivity [this message]
[not found] ` <45FFA790.7080007-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-20 9:25 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45FFA790.7080007@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mingo-X9Un+BFzKDI@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox