All of lore.kernel.org
 help / color / mirror / Atom feed
From: dmukhin@xen.org
To: Mykola Kvach <xakep.amatop@gmail.com>
Cc: xen-devel@lists.xenproject.org, andrew.cooper3@citrix.com,
	anthony.perard@vates.tech, jbeulich@suse.com, julien@xen.org,
	michal.orzel@amd.com, roger.pau@citrix.com,
	sstabellini@kernel.org, dmukhin@ford.com
Subject: Re: [PATCH v6 01/15] emul/vuart: introduce framework for UART emulators
Date: Mon, 8 Sep 2025 02:45:46 -0700	[thread overview]
Message-ID: <aL6lymRB5LtxzDMT@kraken> (raw)
In-Reply-To: <CAGeoDV8xKHSobiLiWuzKtnxPXnRvFWf139BddeTUkuREEvrk2w@mail.gmail.com>

On Mon, Sep 08, 2025 at 11:29:03AM +0300, Mykola Kvach wrote:
> On Sat, Sep 6, 2025 at 2:27 AM <dmukhin@xen.org> wrote:
[..]
> > +++ b/xen/common/emul/vuart/Kconfig
> > @@ -0,0 +1,6 @@
> > +config VUART_FRAMEWORK
> > +       bool
> 
> If VUART_FRAMEWORK has no dependencies, it can be enabled on any
> architecture. For example, I tried enabling it on arm64 and the build
> fails:
> 
>   ./include/xen/vuart.h:26:8: error: redefinition of ‘struct vuart’
> 
> Should this config be restricted (e.g. "depends on X86") or the code
> adjusted to handle non-x86 architectures properly?

Yes, missed that; the code is for x86 only for now.
`struct vuart` on Arm corresponds to simple MMIO-based UART emulator for
hwdom's earlyprintk.

Arm part is pending:
  https://lore.kernel.org/xen-devel/20250624035443.344099-1-dmukhin@ford.com/

Most of the feedback resolved locally, but I need to wait for the other series to land

[..]
> > +static const struct vuart_emulator *
> > +vuart_match_by_compatible(const struct domain *d, const char *compat)
> > +{
> > +    const struct vuart_emulator *emulator;
> > +
> > +    for_each_emulator(emulator)
> > +        if ( emulator->compatible &&
> > +             !strncmp(compat, emulator->compatible,
> > +                      strlen(emulator->compatible)) )
> > +            return emulator;
> > +
> > +    return NULL;
> > +}
> > +
> > +const static struct vuart *
> > +vuart_find_by_console_permission(const struct domain *d)
> 
> During the first review of this patch I thought you planned to add a
> searching procedure into this and the next function in one of the later
> commits. However, looking at the series now, it seems these functions
> remain unchanged and don’t actually perform any searching.
> 
> Do you think the current names are accurate, or would it make sense to
> rename them to better reflect their purpose?

Arm has two vUART emulators enabled by default, so there will be at least two
vUARTs and some search in vuart.c.

I scoped x86 portion of the change into the current series, Arm is to follow,
since I have pending series to plumb vpl011 (i.e. SBSA) and hwdom vuart (i.e.
early dtuart) into that new framework. There will be some adjustments in
vuart.c


  parent reply	other threads:[~2025-09-08  9:45 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 23:26 [PATCH v6 00/15] x86: introduce NS16550-compatible UART emulator dmukhin
2025-09-05 23:27 ` [PATCH v6 01/15] emul/vuart: introduce framework for UART emulators dmukhin
2025-09-06  2:02   ` Stefano Stabellini
2025-09-06  9:43   ` Mykola Kvach
2025-09-08  7:16     ` dmukhin
2025-09-08  8:29   ` Mykola Kvach
2025-09-08  8:43     ` Jan Beulich
2025-09-08  9:45     ` dmukhin [this message]
2025-09-05 23:27 ` [PATCH v6 02/15] xen/8250-uart: update definitions dmukhin
2025-09-06  2:02   ` Stefano Stabellini
2025-09-06 14:57   ` Mykola Kvach
2025-09-08  8:36     ` dmukhin
2025-09-05 23:27 ` [PATCH v6 03/15] emul/ns16x50: implement emulator stub dmukhin
2025-09-06  0:34   ` dmukhin
2025-09-06  2:03   ` Stefano Stabellini
2025-09-06  4:18     ` dmukhin
2025-09-06 20:37   ` Mykola Kvach
2025-09-08  8:32     ` dmukhin
2025-09-08  8:37   ` Mykola Kvach
2025-09-08  9:59     ` dmukhin
2025-09-05 23:27 ` [PATCH v6 04/15] emul/ns16x50: implement DLL/DLM registers dmukhin
2025-09-06  2:03   ` Stefano Stabellini
2025-09-06 21:12   ` Mykola Kvach
2025-09-08  6:41     ` dmukhin
2025-09-05 23:27 ` [PATCH v6 05/15] emul/ns16x50: implement SCR register dmukhin
2025-09-06  2:03   ` Stefano Stabellini
2025-09-06 21:24   ` Mykola Kvach
2025-09-08  3:37     ` dmukhin
2025-09-05 23:27 ` [PATCH v6 06/15] emul/ns16x50: implement IER/IIR registers dmukhin
2025-09-06  1:42   ` Stefano Stabellini
2025-09-08  2:37     ` dmukhin
2025-09-05 23:27 ` [PATCH v6 07/15] emul/ns16x50: implement LCR/LSR registers dmukhin
2025-09-06  2:04   ` Stefano Stabellini
2025-09-05 23:27 ` [PATCH v6 08/15] emul/ns16x50: implement MCR/MSR registers dmukhin
2025-09-06  1:42   ` Stefano Stabellini
2025-09-08  2:35     ` dmukhin
2025-09-05 23:27 ` [PATCH v6 09/15] emul/ns16x50: implement RBR register dmukhin
2025-09-06  2:04   ` Stefano Stabellini
2025-09-05 23:27 ` [PATCH v6 10/15] emul/ns16x50: implement THR register dmukhin
2025-09-06  1:59   ` Stefano Stabellini
2025-09-08  2:50     ` dmukhin
2025-09-08  3:15       ` dmukhin
2025-09-05 23:27 ` [PATCH v6 11/15] emul/ns16x50: implement FCR register (write-only) dmukhin
2025-09-06  2:04   ` Stefano Stabellini
2025-09-05 23:27 ` [PATCH v6 12/15] emul/ns16550: implement dump_state() hook dmukhin
2025-09-05 23:27 ` [PATCH v6 13/15] x86/domain: enable per-domain I/O port bitmaps dmukhin
2025-09-05 23:27 ` [PATCH v6 14/15] xen/domain: allocate d->irq_caps before arch-specific initialization dmukhin
2025-09-05 23:27 ` [PATCH v6 15/15] emul/ns16x50: implement IRQ emulation via vIOAPIC dmukhin
2025-09-06  0:33 ` [PATCH v6 00/15] x86: introduce NS16550-compatible UART emulator dmukhin
2025-09-06  2:01 ` Stefano Stabellini
2025-09-08  9:04   ` Mykola Kvach
2025-09-08 14:19     ` Oleksii Kurochko
2025-09-08 14:23     ` Oleksii Kurochko
2025-09-08 23:51       ` Stefano Stabellini

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=aL6lymRB5LtxzDMT@kraken \
    --to=dmukhin@xen.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=dmukhin@ford.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xakep.amatop@gmail.com \
    --cc=xen-devel@lists.xenproject.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 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.