From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Eric Auger" <eric.auger@redhat.com>,
"David Safford" <safford@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Stefan Berger" <stefanb@linux.ibm.com>
Subject: Re: What is TYPE_TPM_TIS_ISA? (Not an ISA Device)
Date: Tue, 21 Jul 2020 17:40:27 +0100 [thread overview]
Message-ID: <CAFEAcA8b3N+oxAAW3JEKGTtsZezXTOFdnu9Hm1MYK=yURTfVsQ@mail.gmail.com> (raw)
In-Reply-To: <8f5a171a-59db-f5d1-477c-1ddf7af45da7@redhat.com>
On Tue, 21 Jul 2020 at 17:07, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>
> Hi Stefan,
>
> I'm trying to understand what is modelling the
> TYPE_TPM_TIS_ISA device.
>
> It inherits from TYPE_ISA_DEVICE, so I expected
> to see an ISA device, but then I noticed:
>
> 1/ it doesn't use the ISA I/O space, it directly
> maps the device in the system memory at a fixed
> address that is not addressable by the ISA bus:
>
> #define TPM_TIS_ADDR_BASE 0xFED40000
Why do you think this is mapping to the system memory?
tpm_tis_isa_realizefn() does:
memory_region_add_subregion(isa_address_space(ISA_DEVICE(dev)),
TPM_TIS_ADDR_BASE, &s->mmio);
which puts it into the ISA memory address space.
The weird thing about this is not which AS it's
going in but the fact that the TPM_TIS_ADDR_BASE
is way higher than an actual ISA bus can address
(so for instance it's out of range of the size of
the ISA memory window on the Jazz board).
> 2/ it is not plugged to an ISA BUS (ISABus*)
Won't it autoplug into the ISA bus if you say "-device tpm-tis",
the same as any other ISA device ?
> 3/ no machine plug it using isa_register_ioport()
> (it is not registered to the ISA memory space)
There's no requirement for an ISA device to have IO ports...
thanks
-- PMM
next prev parent reply other threads:[~2020-07-21 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 16:02 What is TYPE_TPM_TIS_ISA? (Not an ISA Device) Philippe Mathieu-Daudé
2020-07-21 16:38 ` Stefan Berger
2020-07-21 16:40 ` Peter Maydell [this message]
2020-07-22 5:55 ` Markus Armbruster
2020-07-22 22:07 ` Stefan Berger
2020-07-23 9:10 ` Markus Armbruster
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='CAFEAcA8b3N+oxAAW3JEKGTtsZezXTOFdnu9Hm1MYK=yURTfVsQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=eric.auger@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=safford@us.ibm.com \
--cc=stefanb@linux.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).