qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Francisco Iglesias <francisco.iglesias@amd.com>
Cc: qemu-devel@nongnu.org, frasse.iglesias@gmail.com,
	alistair@alistair23.me,  edgar.iglesias@gmail.com,
	fkonrad@amd.com, sai.pavan.boddu@amd.com,  tong.ho@amd.com,
	vikram.garhwal@amd.com
Subject: Re: [PATCH v3 5/8] hw/misc: Introduce a model of Xilinx Versal's CFRAME_REG
Date: Thu, 31 Aug 2023 16:03:07 +0100	[thread overview]
Message-ID: <CAFEAcA-dbHt4Gvy48eVkobJCMfOivTPfryAgYUBtveebkUqVjA@mail.gmail.com> (raw)
In-Reply-To: <49408ea1-c837-76b8-7a43-de6ac5c682e9@amd.com>

On Thu, 31 Aug 2023 at 16:00, Francisco Iglesias
<francisco.iglesias@amd.com> wrote:
>
> Hi Peter,
>
> On 2023-08-29 18:44, Peter Maydell wrote:
> > You don't need to g_tree_lookup() for every address. If
> > you use g_tree_lookup_node() you get a GTreeNode* back,
> > and you can then iterate through the tree from that point using
> > g_tree_node_next(), something like this:
> >
> >       for (node = g_tree_lookup_node(s->cframes, GUINT_TO_POINTER(addr));
> >            node && GPOINTER_TO_UINT(g_tree_node_key(node)) < end_addr;
> >            node = g_tree_node_next(node)) {
> >           XlnxCFrame *f = g_tree_node_value(node);  // definitely not NULL
> >           /* Transmit the data */
> >           for (int i = 0; i < FRAME_NUM_WORDS; i += 4) {
> >               ... etc ...
> >           }
> >       }
> >
>
> I tried above but it looks to require glib 2.68 so added a comment
> instead (didn't compile on my machine with glib-2.64 :/, if I understand
> meson.build correctly the min glib version supported is 2.56). Let me
> know if some other solution would be preferred.

Whoops, yes, I didn't notice the version-statement on
g_tree_lookup_node(). Yeah, keep what you have.

thanks
-- PMM


  reply	other threads:[~2023-08-31 15:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 18:34 [PATCH v3 0/8] Xilinx Versal CFI support Francisco Iglesias
2023-08-24 18:34 ` [PATCH v3 1/8] hw/misc: Introduce the Xilinx CFI interface Francisco Iglesias
2023-08-24 18:34 ` [PATCH v3 2/8] hw/misc: Introduce a model of Xilinx Versal's CFU_APB Francisco Iglesias
2023-08-24 18:34 ` [PATCH v3 3/8] hw/misc/xlnx-versal-cfu: Introduce a model of Xilinx Versal CFU_FDRO Francisco Iglesias
2023-08-24 18:34 ` [PATCH v3 4/8] hw/misc/xlnx-versal-cfu: Introduce a model of Xilinx Versal's CFU_SFR Francisco Iglesias
2023-08-24 18:34 ` [PATCH v3 5/8] hw/misc: Introduce a model of Xilinx Versal's CFRAME_REG Francisco Iglesias
2023-08-29 16:44   ` Peter Maydell
2023-08-31 14:59     ` Francisco Iglesias
2023-08-31 15:03       ` Peter Maydell [this message]
2023-08-24 18:34 ` [PATCH v3 6/8] hw/misc: Introduce a model of Xilinx Versal's CFRAME_BCAST_REG Francisco Iglesias
2023-08-24 18:34 ` [PATCH v3 7/8] hw/arm/xlnx-versal: Connect the CFU_APB, CFU_FDRO and CFU_SFR Francisco Iglesias
2023-08-24 18:34 ` [PATCH v3 8/8] hw/arm/versal: Connect the CFRAME_REG and CFRAME_BCAST_REG Francisco Iglesias

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=CAFEAcA-dbHt4Gvy48eVkobJCMfOivTPfryAgYUBtveebkUqVjA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alistair@alistair23.me \
    --cc=edgar.iglesias@gmail.com \
    --cc=fkonrad@amd.com \
    --cc=francisco.iglesias@amd.com \
    --cc=frasse.iglesias@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sai.pavan.boddu@amd.com \
    --cc=tong.ho@amd.com \
    --cc=vikram.garhwal@amd.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).