From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: will@kernel.org, julien.thierry.kdev@gmail.com,
kvm@vger.kernel.org, sami.mujawar@arm.com,
lorenzo.pieralisi@arm.com, maz@kernel.org
Subject: Re: [PATCH kvmtool 2/4] arm/fdt.c: Warn if MMIO device doesn't provide a node generator
Date: Thu, 10 Jun 2021 17:38:02 +0100 [thread overview]
Message-ID: <59cefe95-17ef-2ac3-8545-14ec38c0fbe4@arm.com> (raw)
In-Reply-To: <20210610171345.79919d7b@slackpad.fritz.box>
Hi Andre,
On 6/10/21 5:13 PM, Andre Przywara wrote:
> On Wed, 9 Jun 2021 19:38:10 +0100
> Alexandru Elisei <alexandru.elisei@arm.com> wrote:
>
>> Print a more helpful warning when a MMIO device hasn't set a function to
>> generate an FDT instead of causing a segmentation fault by dereferencing a
>> NULL pointer.
> Not calling generate_mmio_fdt_nodes() if it's NULL is certainly a good
> idea, but how did you trigger it?
I was able to trigger it when I was hacking a custom MMIO device emulation to test
some behaviour in KVM.
> Because I am wondering whether every MMIO device needs to have an DT
> generator? And if that's not the case, a warning might be already too
> much.
I don't know how the guest will be able to discover the device if it's not in the
DT, that's why I put the warning. If there are devices which can be discovered by
the guest when they are missing from the DT, then I'll drop the warning.
Thanks,
Alex
>
> So either just drop a print at all or use pr_info()/pr_debug()?
>
> Cheers,
> Andre
>
>> Signed-off-by: Alexandru Elisei <alexandru.elisei@arm.com>
>> ---
>> arm/fdt.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/arm/fdt.c b/arm/fdt.c
>> index 02091e9e0bee..06287a13e395 100644
>> --- a/arm/fdt.c
>> +++ b/arm/fdt.c
>> @@ -171,7 +171,12 @@ static int setup_fdt(struct kvm *kvm)
>> dev_hdr = device__first_dev(DEVICE_BUS_MMIO);
>> while (dev_hdr) {
>> generate_mmio_fdt_nodes = dev_hdr->data;
>> - generate_mmio_fdt_nodes(fdt, dev_hdr, generate_irq_prop);
>> + if (generate_mmio_fdt_nodes) {
>> + generate_mmio_fdt_nodes(fdt, dev_hdr, generate_irq_prop);
>> + } else {
>> + pr_warning("Missing FDT node generator for MMIO device %d",
>> + dev_hdr->dev_num);
>> + }
>> dev_hdr = device__next_dev(dev_hdr);
>> }
>>
next prev parent reply other threads:[~2021-06-10 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 18:38 [PATCH kvmtool 0/4] arm/arm64: PCI Express 1.1 support Alexandru Elisei
2021-06-09 18:38 ` [PATCH kvmtool 1/4] Move fdt_irq_fn typedef to fdt.h Alexandru Elisei
2021-06-10 16:13 ` Andre Przywara
2021-06-09 18:38 ` [PATCH kvmtool 2/4] arm/fdt.c: Warn if MMIO device doesn't provide a node generator Alexandru Elisei
2021-06-10 16:13 ` Andre Przywara
2021-06-10 16:38 ` Alexandru Elisei [this message]
2021-06-14 14:07 ` Andre Przywara
2021-06-14 15:38 ` Alexandru Elisei
2021-06-09 18:38 ` [PATCH kvmtool 3/4] arm/arm64: Add PCI Express 1.1 support Alexandru Elisei
2021-06-10 16:14 ` Andre Przywara
2021-06-10 16:44 ` Alexandru Elisei
2021-06-10 19:00 ` Andre Przywara
2021-06-11 8:51 ` Alexandru Elisei
2021-06-09 18:38 ` [PATCH kvmtool 4/4] arm/arm64: vfio: Add PCI Express Capability Structure Alexandru Elisei
2021-06-10 16:14 ` Andre Przywara
2021-06-10 17:17 ` Alexandru Elisei
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=59cefe95-17ef-2ac3-8545-14ec38c0fbe4@arm.com \
--to=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=sami.mujawar@arm.com \
--cc=will@kernel.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