From: Peter Xu <peterx@redhat.com>
To: kvm@vger.kernel.org
Cc: "David Hildenbrand" <david@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH 0/2] KVM: x86: use pic/ioapic destructor when proper
Date: Wed, 15 Mar 2017 15:58:28 +0800 [thread overview]
Message-ID: <20170315075828.GA5955@pxdev.xzpeter.org> (raw)
In-Reply-To: <1489560811-32237-1-git-send-email-peterx@redhat.com>
On Wed, Mar 15, 2017 at 02:53:29PM +0800, Peter Xu wrote:
> A tiny cleanup series for pic/ioapic destruction when vm destroys.
> Please review, Thanks.
>
> Peter Xu (2):
> KVM: x86: clear bus pointer when destroyed
> KVM: x86: use pic/ioapic destructor when destroy vm
NACK. Patch 2 breaks split irqchip.
The old code can live with split irqchip since it's using kfree() and
kfree() allows null pointer. Will repost. Sorry for the noise...
-- peterx
prev parent reply other threads:[~2017-03-15 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 6:53 [PATCH 0/2] KVM: x86: use pic/ioapic destructor when proper Peter Xu
2017-03-15 6:53 ` [PATCH 1/2] KVM: x86: clear bus pointer when destroyed Peter Xu
2017-03-15 6:53 ` [PATCH 2/2] KVM: x86: use pic/ioapic destructor when destroy vm Peter Xu
2017-03-15 7:58 ` Peter Xu [this message]
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=20170315075828.GA5955@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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.