From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: KVM <kvm@vger.kernel.org>, Gleb Natapov <gleb@kernel.org>,
Rik van Riel <riel@redhat.com>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
Michael Mueller <mimu@linux.vnet.ibm.com>
Subject: Re: [PATCH/RFC] KVM: track pid for VCPU only on KVM_RUN ioctl
Date: Tue, 19 Aug 2014 12:31:41 +0200 [thread overview]
Message-ID: <53F3278D.9070107@redhat.com> (raw)
In-Reply-To: <53F32267.6090106@de.ibm.com>
Il 19/08/2014 12:09, Christian Borntraeger ha scritto:
>> I'm not sure, this does seem like a workaround for another
>> limitation after all... Gleb?
>
> Yes. We want to get rid of KVM_S390_INITIAL_RESET in QEMU. This comes
> from a time, when we had another userspace prototype for KVM on s390
> (kuli). Its really a wart that has to go. Its just that we are not
> there yet to remove the call to KVM_S390_INITIAL_RESET. Doing so can
> result in hard to debug errors after reboot, if an interrupt was made
> pending just before reboot that gets delivered in the new instance.
>
> The new way for local interrupt read/write will probably be some
> onereg or syncreg interface with a bitmask register and payload
> registers. We have to solve some concurrency and implemenation issues
> here.
Yes, I understand; the plan is fine and it's good that it was already on
your todo list.
But since you acknowledge that KVM_S390_INITIAL_RESET will go, I'm not
sure we want to apply this patch (except for the pid == 0 part, of
course---that one is good).
Paolo
next prev parent reply other threads:[~2014-08-19 10:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 14:44 [PATCH/RFC] KVM: track pid for VCPU only on KVM_RUN ioctl Christian Borntraeger
2014-08-07 8:21 ` Raghavendra K T
2014-08-07 9:59 ` Christian Borntraeger
2014-08-07 13:40 ` Paolo Bonzini
2014-08-19 8:38 ` Christian Borntraeger
2014-08-07 13:39 ` Paolo Bonzini
2014-08-19 8:38 ` Christian Borntraeger
2014-08-19 9:27 ` Paolo Bonzini
2014-08-19 9:47 ` Christian Borntraeger
2014-08-19 9:53 ` Paolo Bonzini
2014-08-19 9:59 ` Christian Borntraeger
2014-08-19 10:03 ` Paolo Bonzini
2014-08-19 10:09 ` Christian Borntraeger
2014-08-19 10:31 ` Paolo Bonzini [this message]
2014-08-19 10:48 ` Christian Borntraeger
2014-08-19 10:50 ` Paolo Bonzini
2014-08-19 11:28 ` David Hildenbrand
2014-08-19 12:06 ` Paolo Bonzini
2014-08-19 12:14 ` David Hildenbrand
2014-08-19 14:10 ` Christian Borntraeger
2014-08-19 14:23 ` David Hildenbrand
2014-08-19 14:46 ` Christian Borntraeger
2014-08-19 14:52 ` David Hildenbrand
2014-08-18 5:02 ` Wanpeng Li
2014-08-19 14:04 ` Christian Borntraeger
2014-08-19 23:22 ` Wanpeng Li
2014-08-20 7:01 ` Christian Borntraeger
2014-12-03 13:20 ` Paolo Bonzini
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=53F3278D.9070107@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mimu@linux.vnet.ibm.com \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=riel@redhat.com \
/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.