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 03/15] emul/ns16x50: implement emulator stub
Date: Mon, 8 Sep 2025 02:59:18 -0700 [thread overview]
Message-ID: <aL6o9u0t6rtFFfaA@kraken> (raw)
In-Reply-To: <CAGeoDV8cGyKZCXpm=U5FkjBi701T2Cku39DM9iFMGRUBFN5mPA@mail.gmail.com>
On Mon, Sep 08, 2025 at 11:37:03AM +0300, Mykola Kvach wrote:
> > --- a/xen/common/emul/vuart/Kconfig
> > +++ b/xen/common/emul/vuart/Kconfig
> > @@ -3,4 +3,23 @@ config VUART_FRAMEWORK
> >
> > menu "UART Emulation"
> >
> > +config VUART_NS16X50
> > + bool "NS16550-compatible UART Emulator" if EXPERT
> > + depends on X86 && HVM
>
> Currently VUART_NS16X50 depends on X86, so the code is only
> usable on x86. Are there any plans to support this vUART on non-x86
> architectures (e.g. ARM, where some UARTs are also ns16550-compatible)?
The plan is to add MMIO-based implementation for x86 first.
>
> If not, wouldn’t it be more appropriate to move the ns16x50-specific
> implementation into x86-specific directories instead of common?
There was discussion on that and the agreement is to move all vUARTs into
common/emul/vuart
and start using common/emul as a placeholder for common emulation code,
including vPCI.
next prev parent reply other threads:[~2025-09-08 9:59 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
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 [this message]
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=aL6o9u0t6rtFFfaA@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.