From: Igor Mammedov <imammedo@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
Stefan Berger <stefanb@us.ibm.com>,
crobinso@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] acpi: tpm: Fix TPM ACPI description
Date: Fri, 8 Apr 2016 10:13:02 +0200 [thread overview]
Message-ID: <20160408101302.240a177c@nial.brq.redhat.com> (raw)
In-Reply-To: <20160408105013-mutt-send-email-mst@redhat.com>
On Fri, 8 Apr 2016 10:51:30 +0300
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Mon, Apr 04, 2016 at 02:11:05PM +0200, Igor Mammedov wrote:
> > On Mon, 4 Apr 2016 06:31:43 -0400
> > Stefan Berger <stefanb@linux.vnet.ibm.com> wrote:
> >
> > > On 04/04/2016 05:04 AM, Michael S. Tsirkin wrote:
> > > > On Sun, Apr 03, 2016 at 09:37:54PM -0400, Stefan Berger wrote:
> > > >> This series of patches fixes some problems with the TPM's ACPI
> > > >> description.
> > > > Could you pls describe how does this interact with Igor's patch?
> > >
> > > Follow https://bugzilla.redhat.com/attachment.cgi?id=1137429 and
> > > attachment https://bugzilla.redhat.com/attachment.cgi?id=1137429 I
> > > don't think we need Igor's patch. I am posting what has been tested.
> > I've also tested my patch + commented out irq, it also 'works'.
> > i.e. Windows doesn't see irq conflict as well.
>
> Igor, could you please post a complete patchset for testing?
> It seems preferable to me.
Ok, I'll post a2 patches, 1st adding range to PCI0._CRS and
2nd commenting out IRQ entry with a hope that Stefan will fix
IRQ handling in 2.7 dev cycle.
>
> > >
> > > >
> > > >
> > > >> Stefan Berger (2):
> > > >> acpi: tpm: Fix TPM ACPI description (BZ 1281413)
> > > >> acpi: tpm: Get the interrupt the device model is using
> > > >>
> > > >> hw/i386/acpi-build.c | 29 ++++++++++++++---------------
> > > >> hw/tpm/tpm_tis.c | 5 ++++-
> > > >> include/sysemu/tpm.h | 6 +++---
> > > >> 3 files changed, 21 insertions(+), 19 deletions(-)
> > > >>
> > > >> --
> > > >> 2.5.5
> > >
next prev parent reply other threads:[~2016-04-08 8:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 1:37 [Qemu-devel] [PATCH 0/2] acpi: tpm: Fix TPM ACPI description Stefan Berger
2016-04-04 1:37 ` [Qemu-devel] [PATCH 1/2] acpi: tpm: Fix TPM ACPI description (BZ 1281413) Stefan Berger
2016-04-04 9:04 ` Michael S. Tsirkin
2016-04-04 10:17 ` Stefan Berger
2016-04-04 11:49 ` Igor Mammedov
2016-04-04 1:37 ` [Qemu-devel] [PATCH 2/2] acpi: tpm: Get the interrupt the device model is using Stefan Berger
2016-04-04 9:01 ` Michael S. Tsirkin
2016-04-04 10:10 ` Stefan Berger
2016-04-04 10:12 ` Michael S. Tsirkin
2016-04-04 12:08 ` Igor Mammedov
2016-04-04 9:04 ` [Qemu-devel] [PATCH 0/2] acpi: tpm: Fix TPM ACPI description Michael S. Tsirkin
2016-04-04 10:31 ` Stefan Berger
2016-04-04 12:11 ` Igor Mammedov
2016-04-08 7:51 ` Michael S. Tsirkin
2016-04-08 8:13 ` Igor Mammedov [this message]
2016-04-04 16:00 ` Michael S. Tsirkin
2016-04-06 0:13 ` Stefan Berger
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=20160408101302.240a177c@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=crobinso@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanb@us.ibm.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 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).