From: Jan Kiszka <jan.kiszka@web.de>
To: kvm-ppc@vger.kernel.org
Subject: Re: Guest reboot interface
Date: Fri, 07 Jan 2011 15:38:35 +0000 [thread overview]
Message-ID: <4D27337B.8010001@web.de> (raw)
In-Reply-To: <FBDE6FBB4662C043AC9EECB95F62CDDE0727AA@039-SN1MPN1-004.039d.mgd.msft.net>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Am 07.01.2011 13:40, Alexander Graf wrote:
>
> On 07.01.2011, at 13:08, Liu Yu-B13201 wrote:
>
>>
>> Hi all,
>>
>> When guest reboot, it's better to reset status by qemu, and then sync them back to kvm
>> However as you know there's no BOOKE mmu emulation in qemu,
>> So that qemu cannot directly reset BOOKE TLB.
>> Moreover a lot SPR registers also cannot be reset by qemu.
>>
>> As a workaround, we need a interface that qemu can notify kvm to reset the status.
>> My question is, what should the interface be?
>> Looks like there's no alike interface in other archs.
>> Should we define a ioctl command number only used by BOOKE or powerpc?
>
> Wouldn't it make more sense to just fake-implement the registers (SPRs and unused TLB) and sync that back on reset? You don't have to implement the actual mmu logic, but that keeps things at the same place at least.
>
This is how it's done on x86, and it's the preferred way. There will
never be such things as KVM_IOCTL_RESET.
BTW, isn't the TLB state relevant for vmsave/restore? Then it should be
made accessible for user space anyway.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-01-07 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 12:08 Guest reboot interface Liu Yu-B13201
2011-01-07 12:40 ` Alexander Graf
2011-01-07 15:38 ` Jan Kiszka [this message]
2011-01-07 17:20 ` Scott Wood
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=4D27337B.8010001@web.de \
--to=jan.kiszka@web.de \
--cc=kvm-ppc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.