Re: [PATCH v3 15/24] xen/console: make console buffer size configurable

[Denis Mukhin <dmkhn@xxxxxxxxx>]

On Tuesday, January 28th, 2025 at 11:53 PM, Jan Beulich <jbeulich@xxxxxxxx> 
wrote:

> 
> 
> On 29.01.2025 04:04, Denis Mukhin wrote:
> 
> > On Tuesday, January 28th, 2025 at 8:32 AM, Jan Beulich jbeulich@xxxxxxxx 
> > wrote:
> > 
> > > On 04.01.2025 02:58, Denis Mukhin via B4 Relay wrote:
> > > 
> > > > From: Denis Mukhin dmukhin@xxxxxxxx
> > > > 
> > > > Add new CONRING_SIZE Kconfig parameter to specify the boot console 
> > > > buffer size
> > > > in bytes. The value is rounded to the nearest power of 2 to match 
> > > > existing
> > > > conring_size= behavior.
> > > > 
> > > > The supported range is [16KiB..128MiB].
> > > > 
> > > > Bump default size to 32 KiB.
> > > > 
> > > > Link: https://gitlab.com/xen-project/xen/-/issues/185
> > > > Signed-off-by: Denis Mukhin dmukhin@xxxxxxxx
> > > 
> > > As asked elsewhere already: How's this related to the goal of the series?
> > 
> > I mentioned in the cover letter that there are two group of patches - 
> > console
> > driver cleanups/fixes and the follow on UART emulator (and up until v3 it 
> > was OK
> > to have this patch bundled into the series).
> > 
> > Yes, I acknowledge that the first group of patches for console driver grew 
> > big
> > and probably should have been posted in its own thread.
> > 
> > I can move "console" part to its own series if it makes sense now.
> > 
> > What do you think?
> 
> 
> I for one would appreciate you doing so. Where patches are independent, you
> may even want to consider posting them individually. That way it'll be clear
> they're isolated, and hence any one of them that is fully reviewed/acked can
> go in (once the tree is fully open again).

Moved patch to a separate thread:
  https://lore.kernel.org/xen-devel/20250212222157.2974150-1-dmukhin@xxxxxxxx/

> 
> Jan