From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/3] q35: set split kernel irqchip as default
Date: Fri, 3 May 2019 16:00:33 -0400 [thread overview]
Message-ID: <20190503155951-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190429145556.GA28722@habkost.net>
On Mon, Apr 29, 2019 at 11:55:56AM -0300, Eduardo Habkost wrote:
> irqchip=split and irqchip=kernel aren't guest ABI compatible, are
> they?
Can you remind me why they aren't?
> --
> Eduardo
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/3] q35: set split kernel irqchip as default
Date: Fri, 3 May 2019 16:00:33 -0400 [thread overview]
Message-ID: <20190503155951-mutt-send-email-mst@kernel.org> (raw)
Message-ID: <20190503200033.c_9TwEdpanXhZ4OaSDDmyH23kAPSjvQPUhE_BjxIyWY@z> (raw)
In-Reply-To: <20190429145556.GA28722@habkost.net>
On Mon, Apr 29, 2019 at 11:55:56AM -0300, Eduardo Habkost wrote:
> irqchip=split and irqchip=kernel aren't guest ABI compatible, are
> they?
Can you remind me why they aren't?
> --
> Eduardo
next prev parent reply other threads:[~2019-05-03 20:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 5:40 [Qemu-devel] [PATCH v2 0/3] q35: change defaults for kernel irqchip and IR Peter Xu
2018-12-20 5:40 ` [Qemu-devel] [PATCH v2 1/3] q35: set split kernel irqchip as default Peter Xu
2018-12-20 12:13 ` Eduardo Habkost
2019-04-26 19:27 ` Alex Williamson
2019-04-26 19:27 ` Alex Williamson
2019-04-26 21:02 ` Alex Williamson
2019-04-26 21:02 ` Alex Williamson
2019-04-27 5:29 ` Paolo Bonzini
2019-04-27 5:29 ` Paolo Bonzini
2019-04-27 8:09 ` Paolo Bonzini
2019-04-27 8:09 ` Paolo Bonzini
2019-04-29 14:21 ` Alex Williamson
2019-04-29 14:21 ` Alex Williamson
2019-04-29 14:55 ` Eduardo Habkost
2019-04-29 14:55 ` Eduardo Habkost
2019-04-29 15:22 ` Alex Williamson
2019-04-29 15:22 ` Alex Williamson
2019-05-03 18:42 ` Eduardo Habkost
2019-05-03 18:42 ` Eduardo Habkost
2019-05-05 9:06 ` Peter Xu
2019-05-05 9:06 ` Peter Xu
2019-05-06 16:13 ` Paolo Bonzini
2019-05-06 21:16 ` Eduardo Habkost
2019-05-03 20:00 ` Michael S. Tsirkin [this message]
2019-05-03 20:00 ` Michael S. Tsirkin
2019-05-03 20:23 ` Eduardo Habkost
2019-05-03 20:23 ` Eduardo Habkost
2019-05-06 16:17 ` Paolo Bonzini
2019-04-30 23:01 ` Alex Williamson
2019-04-30 23:01 ` Alex Williamson
2019-04-30 23:09 ` Paolo Bonzini
2019-04-30 23:09 ` Paolo Bonzini
2019-05-01 0:28 ` Alex Williamson
2019-05-01 0:28 ` Alex Williamson
2018-12-20 5:40 ` [Qemu-devel] [PATCH v2 2/3] x86-iommu: switch intr_supported to OnOffAuto type Peter Xu
2018-12-20 5:40 ` [Qemu-devel] [PATCH v2 3/3] x86-iommu: turn on IR by default if proper Peter Xu
2018-12-20 10:00 ` [Qemu-devel] [PATCH v2 0/3] q35: change defaults for kernel irqchip and IR Paolo Bonzini
2018-12-20 10:16 ` Peter Xu
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=20190503155951-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).