From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH qemu v2] spapr: Kill SLOF
Date: Thu, 9 Jan 2020 15:25:13 +1100 [thread overview]
Message-ID: <20200109042513.GO8586@umbus.fritz.box> (raw)
In-Reply-To: <90bb7907-5b81-45e4-b227-e037f41af67e@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]
On Wed, Jan 08, 2020 at 04:53:06PM +1100, Alexey Kardashevskiy wrote:
>
>
> On 08/01/2020 15:20, Alexey Kardashevskiy wrote:
> >
> >
> > On 07/01/2020 16:54, David Gibson wrote:
> >> On Tue, Jan 07, 2020 at 03:44:35PM +1100, Alexey Kardashevskiy wrote:
> >>>
> >>>
> >>> On 06/01/2020 15:19, David Gibson wrote:
> >>>>> +
> >>>>> +static uint32_t client_package_to_path(const void *fdt, uint32_t phandle,
> >>>>> + uint32_t buf, uint32_t len)
> >>>>> +{
> >>>>> + char tmp[256];
> >>>>
> >>>> Fixed sized buffers are icky. You could either dynamically allocate
> >>>> this based on the size the client gives, or you could use
> >>>> memory_region_get_ram_ptr() to read the data from the tree directly
> >>>> into guest memory.
> >>>
> >>> @len comes from the guest, I am really not comfortable with allocating
> >>> whatever (broken) guest requested. And if I limit @len by 1024 or
> >>> similar, then a fixed size buffer will do too, no?
> >>
> >> I see your point. Does this call have a way to report failure? In
> >> that case you could outright fail the call if it requests too long a
> >> length.
> >
> > It returns length which can be 0 to signal an error.
> >
> > but with this particular method the bigger problem is that I cannot know
> > in advance the actual path length from fdt_get_path(). I could double
> > the size until fdt_get_path() succeeded, just seems overkill here.
> >
> > Property names seem to be limited by 32:
>
>
> >>> len("ibm,query-interrupt-source-number")
> 33
>
> Awesome. Oh well :(
Yeah, as I suspected. Also 'ibm,associativity-reference-points'.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-09 4:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 23:42 [PATCH qemu v2] spapr: Kill SLOF Alexey Kardashevskiy
2020-01-06 4:19 ` David Gibson
2020-01-06 6:28 ` Alexey Kardashevskiy
2020-01-06 8:50 ` David Gibson
2020-01-06 12:34 ` Alexey Kardashevskiy
2020-01-06 17:09 ` Cédric Le Goater
2020-01-06 17:25 ` Peter Maydell
2020-01-06 18:56 ` Philippe Mathieu-Daudé
2020-01-07 1:44 ` Alexey Kardashevskiy
2020-01-07 5:26 ` David Gibson
2020-01-08 4:07 ` Alexey Kardashevskiy
2020-01-09 4:07 ` David Gibson
2020-01-09 6:31 ` Alexey Kardashevskiy
2020-01-13 3:32 ` David Gibson
2020-01-06 13:39 ` Alexey Kardashevskiy
2020-01-06 23:56 ` David Gibson
2020-01-07 4:44 ` Alexey Kardashevskiy
2020-01-07 5:54 ` David Gibson
2020-01-08 4:20 ` Alexey Kardashevskiy
2020-01-08 5:53 ` Alexey Kardashevskiy
2020-01-09 4:25 ` David Gibson [this message]
2020-01-09 4:18 ` David Gibson
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=20200109042513.GO8586@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).