All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: Guenter Roeck <linux@roeck-us.net>, Palmer Dabbelt <palmer@dabbelt.com>
Cc: Bin Meng <bin.meng@windriver.com>,
	Weiwei Li <liweiwei@iscas.ac.cn>,
	Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
	qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
	Alistair Francis <alistair23@gmail.com>
Subject: Re: [PATCH] riscv: Generate devicetree only after machine initialization is complete
Date: Mon, 3 Jul 2023 19:35:50 -0300	[thread overview]
Message-ID: <db92935e-fd9a-32e9-09d4-052da4e5e61a@ventanamicro.com> (raw)
In-Reply-To: <48537c03-786a-e85b-7db3-ab69939de7ab@roeck-us.net>



On 7/3/23 18:18, Guenter Roeck wrote:
> On 7/3/23 12:25, Daniel Henrique Barboza wrote:
>> On 7/3/23 00:46, Guenter Roeck wrote:
>>> If the devicetree is created before machine initialization is complete,
>>> it misses dynamic devices. Specifically, the tpm device is not added
>>> to the devicetree file and is therefore not instantiated in Linux.
>>> Create devicetree in virt_machine_done() to solve the problem.
>>>
>>> Cc: Alistair Francis <alistair23@gmail.com>
>>> Fixes: 325b7c4e75 hw/riscv: Enable TPM backends
>>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>>> ---
>>>   hw/riscv/virt.c | 9 ++++++---
>>>   1 file changed, 6 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c
>>> index ed4c27487e..08876284f5 100644
>>> --- a/hw/riscv/virt.c
>>> +++ b/hw/riscv/virt.c
>>> @@ -1248,6 +1248,11 @@ static void virt_machine_done(Notifier *notifier, void *data)
>>>       uint64_t kernel_entry = 0;
>>>       BlockBackend *pflash_blk0;
>>> +    /* create devicetree if not provided */
>>> +    if (!machine->dtb) {
>>> +        create_fdt(s, memmap);
>>> +    }
>>> +
>>
>> I suggest moving the entire load/create DT code from virt_machine_init() to
>> the start of virt_machine_done():
>>
>>      /* load/create device tree */
>>      if (machine->dtb) {
>>          machine->fdt = load_device_tree(machine->dtb, &s->fdt_size);
>>          if (!machine->fdt) {
>>              error_report("load_device_tree() failed");
>>              exit(1);
>>          }
>>      } else {
>>          create_fdt(s, memmap);
>>      }
>>
>> This way we don't have to look in to 2 different functions to wonder what happens
>> in case machine->dtb is NULL.
>>
> 
> I can do that, but I don't know how to test it. Is there a working dtb/machine
> combination for riscv which would let me test loading a devicetree file ?

I recommend using your own setup with TPM (I'm assuming you're using a TPM setup),
generate a .dtb from it, and then launch it using '-dtb'.

First you need the patch applied (otherwise there won't be a TPM in the FDT).
After that, relaunch the same machine again but appending in the end of the
command line:

-machine dumpdtb=file.dtb

This will create a 'file.dtb' file in the working dir and exit. After that re-launch
the machine again but now append:

-dtb file.dtb

And you should be able to boot a 'virt' machine with TPM support.


Thanks,

Daniel



> 
> Guenter
> 


      reply	other threads:[~2023-07-03 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  3:46 [PATCH] riscv: Generate devicetree only after machine initialization is complete Guenter Roeck
2023-07-03  7:46 ` Philippe Mathieu-Daudé
2023-07-03 14:10   ` Guenter Roeck
2023-07-03 19:10   ` Daniel Henrique Barboza
2023-07-03 19:25 ` Daniel Henrique Barboza
2023-07-03 21:18   ` Guenter Roeck
2023-07-03 22:35     ` Daniel Henrique Barboza [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=db92935e-fd9a-32e9-09d4-052da4e5e61a@ventanamicro.com \
    --to=dbarboza@ventanamicro.com \
    --cc=alistair23@gmail.com \
    --cc=bin.meng@windriver.com \
    --cc=linux@roeck-us.net \
    --cc=liweiwei@iscas.ac.cn \
    --cc=palmer@dabbelt.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=zhiwei_liu@linux.alibaba.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.