All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: Will Deacon <will@kernel.org>,
	Julien Thierry <julien.thierry.kdev@gmail.com>,
	kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org,
	Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH kvmtool 02/21] hw/serial: Use device abstraction for FDT generator function
Date: Thu, 11 Feb 2021 17:45:47 +0000	[thread overview]
Message-ID: <20210211174547.2bf5a5a0@slackpad.fritz.box> (raw)
In-Reply-To: <d0fbeccf-ecf6-5b53-c165-67a531e79e45@arm.com>

On Thu, 11 Feb 2021 12:05:35 +0000
Alexandru Elisei <alexandru.elisei@arm.com> wrote:

Hi,

> On 12/10/20 2:28 PM, Andre Przywara wrote:
> > At the moment we use the .generate_fdt_node member of the ioport ops
> > structure to store the function pointer for the FDT node generator
> > function. ioport__register() will then put a wrapper and this pointer
> > into the device header.
> > The serial device is the only device making use of this special ioport
> > feature, so let's move this over to using the device header directly.
> >
> > This will allow us to get rid of this .generate_fdt_node member in the
> > ops and simplify the code.
> >
> > Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> > ---
> >  hw/serial.c       | 49 +++++++++++++++++++++++++++++++++++++----------
> >  include/kvm/kvm.h |  2 ++
> >  2 files changed, 41 insertions(+), 10 deletions(-)
> >
> > diff --git a/hw/serial.c b/hw/serial.c
> > index 13c4663e..b0465d99 100644
> > --- a/hw/serial.c
> > +++ b/hw/serial.c
> > @@ -23,6 +23,7 @@
> >  #define UART_IIR_TYPE_BITS	0xc0
> >  
> >  struct serial8250_device {
> > +	struct device_header	dev_hdr;
> >  	struct mutex		mutex;
> >  	u8			id;
> >  
> > @@ -53,9 +54,20 @@ struct serial8250_device {
> >  	.msr			= UART_MSR_DCD | UART_MSR_DSR | UART_MSR_CTS, \
> >  	.mcr			= UART_MCR_OUT2,
> >  
> > +#ifdef CONFIG_HAS_LIBFDT
> > +static
> > +void serial8250_generate_fdt_node(void *fdt, struct device_header *dev_hdr,
> > +				  fdt_irq_fn irq_fn);
> > +#else
> > +#define serial8250_generate_fdt_node	NULL
> > +#endif
> >  static struct serial8250_device devices[] = {
> >  	/* ttyS0 */
> >  	[0]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 0,
> > @@ -66,6 +78,10 @@ static struct serial8250_device devices[] = {
> >  	},
> >  	/* ttyS1 */
> >  	[1]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 1,
> > @@ -76,6 +92,10 @@ static struct serial8250_device devices[] = {
> >  	},
> >  	/* ttyS2 */
> >  	[2]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 2,
> > @@ -86,6 +106,10 @@ static struct serial8250_device devices[] = {
> >  	},
> >  	/* ttyS3 */
> >  	[3]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 3,
> > @@ -371,13 +395,14 @@ char *fdt_stdout_path = NULL;
> >  
> >  #define DEVICE_NAME_MAX_LEN 32
> >  static
> > -void serial8250_generate_fdt_node(struct ioport *ioport, void *fdt,
> > -				  void (*generate_irq_prop)(void *fdt,
> > -							    u8 irq,
> > -							    enum irq_type))
> > +void serial8250_generate_fdt_node(void *fdt, struct device_header *dev_hdr,
> > +				  fdt_irq_fn irq_fn)
> >  {
> >  	char dev_name[DEVICE_NAME_MAX_LEN];
> > -	struct serial8250_device *dev = ioport->priv;
> > +	struct serial8250_device *dev = container_of(dev_hdr,
> > +						     struct serial8250_device,
> > +						     dev_hdr);
> > +
> >  	u64 addr = KVM_IOPORT_AREA + dev->iobase;
> >  	u64 reg_prop[] = {
> >  		cpu_to_fdt64(addr),
> > @@ -395,24 +420,26 @@ void serial8250_generate_fdt_node(struct ioport *ioport, void *fdt,
> >  	_FDT(fdt_begin_node(fdt, dev_name));
> >  	_FDT(fdt_property_string(fdt, "compatible", "ns16550a"));
> >  	_FDT(fdt_property(fdt, "reg", reg_prop, sizeof(reg_prop)));
> > -	generate_irq_prop(fdt, dev->irq, IRQ_TYPE_LEVEL_HIGH);
> > +	irq_fn(fdt, dev->irq, IRQ_TYPE_LEVEL_HIGH);
> >  	_FDT(fdt_property_cell(fdt, "clock-frequency", 1843200));
> >  	_FDT(fdt_end_node(fdt));
> >  }
> > -#else
> > -#define serial8250_generate_fdt_node	NULL
> >  #endif
> >  
> >  static struct ioport_operations serial8250_ops = {
> >  	.io_in			= serial8250_in,
> >  	.io_out			= serial8250_out,
> > -	.generate_fdt_node	= serial8250_generate_fdt_node,
> >  };
> >  
> > -static int serial8250__device_init(struct kvm *kvm, struct serial8250_device *dev)
> > +static int serial8250__device_init(struct kvm *kvm,
> > +				   struct serial8250_device *dev)
> >  {
> >  	int r;
> >  
> > +	r = device__register(&dev->dev_hdr);
> > +	if (r < 0)
> > +		return r;
> > +
> >  	ioport__map_irq(&dev->irq);
> >  	r = ioport__register(kvm, dev->iobase, &serial8250_ops, 8, dev);  
> 
> It's unfortunate that we now create two devices for one serial instance: one here,
> and one created by ioport__register(). But I guess that's unavoidable in this
> patch, and later patches will remove it.

Well, we do this already, wherever we register multiple I/O ports per
device, RTC and i8042 are an example (because we register one device
per I/O port). This really isn't a particular problem, it's just ugly,
so just get's a tiny bit more uglier for a few patches that
hopefully nobody will actually use (in anger).

> 
> >  
> > @@ -438,6 +465,7 @@ cleanup:
> >  		struct serial8250_device *dev = &devices[j];
> >  
> >  		ioport__unregister(kvm, dev->iobase);
> > +		device__unregister(&dev->dev_hdr);
> >  	}
> >  
> >  	return r;
> > @@ -455,6 +483,7 @@ int serial8250__exit(struct kvm *kvm)
> >  		r = ioport__unregister(kvm, dev->iobase);
> >  		if (r < 0)
> >  			return r;
> > +		device__unregister(&dev->dev_hdr);
> >  	}
> >  
> >  	return 0;
> > diff --git a/include/kvm/kvm.h b/include/kvm/kvm.h
> > index 53373b08..ee99c28e 100644
> > --- a/include/kvm/kvm.h
> > +++ b/include/kvm/kvm.h
> > @@ -31,6 +31,8 @@
> >  	.name = #ext,			\
> >  	.code = ext
> >  
> > +typedef void (*fdt_irq_fn)(void *fdt, u8 irq, enum irq_type);  
> 
> Shouldn't that last parameter be enum irq_type irq_type? Would you consider moving
> the typedef to include/kvm/fdt.h?

I think where I came from was that typedef's don't need parameter names,
just the type. But just having (void *, u8, enum irq_type) is really
hard to understand, so I added parameter names where this helps. "enum
irq_type irq_type" looks redundant, but I can certainly add this for
consistency.

> Other than the nitpicks above, the patch looks sound to me. I also did a quick
> test by running kvm-unit-tests:
> 
> Reviewed-by: Alexandru Elisei <alexandru.elisei@arm.com>

Thanks!

Andre

> 
> Thanks,
> Alex
> > +
> >  enum {
> >  	KVM_VMSTATE_RUNNING,
> >  	KVM_VMSTATE_PAUSED,  


WARNING: multiple messages have this Message-ID (diff)
From: Andre Przywara <andre.przywara@arm.com>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: kvm@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
	Will Deacon <will@kernel.org>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH kvmtool 02/21] hw/serial: Use device abstraction for FDT generator function
Date: Thu, 11 Feb 2021 17:45:47 +0000	[thread overview]
Message-ID: <20210211174547.2bf5a5a0@slackpad.fritz.box> (raw)
In-Reply-To: <d0fbeccf-ecf6-5b53-c165-67a531e79e45@arm.com>

On Thu, 11 Feb 2021 12:05:35 +0000
Alexandru Elisei <alexandru.elisei@arm.com> wrote:

Hi,

> On 12/10/20 2:28 PM, Andre Przywara wrote:
> > At the moment we use the .generate_fdt_node member of the ioport ops
> > structure to store the function pointer for the FDT node generator
> > function. ioport__register() will then put a wrapper and this pointer
> > into the device header.
> > The serial device is the only device making use of this special ioport
> > feature, so let's move this over to using the device header directly.
> >
> > This will allow us to get rid of this .generate_fdt_node member in the
> > ops and simplify the code.
> >
> > Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> > ---
> >  hw/serial.c       | 49 +++++++++++++++++++++++++++++++++++++----------
> >  include/kvm/kvm.h |  2 ++
> >  2 files changed, 41 insertions(+), 10 deletions(-)
> >
> > diff --git a/hw/serial.c b/hw/serial.c
> > index 13c4663e..b0465d99 100644
> > --- a/hw/serial.c
> > +++ b/hw/serial.c
> > @@ -23,6 +23,7 @@
> >  #define UART_IIR_TYPE_BITS	0xc0
> >  
> >  struct serial8250_device {
> > +	struct device_header	dev_hdr;
> >  	struct mutex		mutex;
> >  	u8			id;
> >  
> > @@ -53,9 +54,20 @@ struct serial8250_device {
> >  	.msr			= UART_MSR_DCD | UART_MSR_DSR | UART_MSR_CTS, \
> >  	.mcr			= UART_MCR_OUT2,
> >  
> > +#ifdef CONFIG_HAS_LIBFDT
> > +static
> > +void serial8250_generate_fdt_node(void *fdt, struct device_header *dev_hdr,
> > +				  fdt_irq_fn irq_fn);
> > +#else
> > +#define serial8250_generate_fdt_node	NULL
> > +#endif
> >  static struct serial8250_device devices[] = {
> >  	/* ttyS0 */
> >  	[0]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 0,
> > @@ -66,6 +78,10 @@ static struct serial8250_device devices[] = {
> >  	},
> >  	/* ttyS1 */
> >  	[1]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 1,
> > @@ -76,6 +92,10 @@ static struct serial8250_device devices[] = {
> >  	},
> >  	/* ttyS2 */
> >  	[2]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 2,
> > @@ -86,6 +106,10 @@ static struct serial8250_device devices[] = {
> >  	},
> >  	/* ttyS3 */
> >  	[3]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 3,
> > @@ -371,13 +395,14 @@ char *fdt_stdout_path = NULL;
> >  
> >  #define DEVICE_NAME_MAX_LEN 32
> >  static
> > -void serial8250_generate_fdt_node(struct ioport *ioport, void *fdt,
> > -				  void (*generate_irq_prop)(void *fdt,
> > -							    u8 irq,
> > -							    enum irq_type))
> > +void serial8250_generate_fdt_node(void *fdt, struct device_header *dev_hdr,
> > +				  fdt_irq_fn irq_fn)
> >  {
> >  	char dev_name[DEVICE_NAME_MAX_LEN];
> > -	struct serial8250_device *dev = ioport->priv;
> > +	struct serial8250_device *dev = container_of(dev_hdr,
> > +						     struct serial8250_device,
> > +						     dev_hdr);
> > +
> >  	u64 addr = KVM_IOPORT_AREA + dev->iobase;
> >  	u64 reg_prop[] = {
> >  		cpu_to_fdt64(addr),
> > @@ -395,24 +420,26 @@ void serial8250_generate_fdt_node(struct ioport *ioport, void *fdt,
> >  	_FDT(fdt_begin_node(fdt, dev_name));
> >  	_FDT(fdt_property_string(fdt, "compatible", "ns16550a"));
> >  	_FDT(fdt_property(fdt, "reg", reg_prop, sizeof(reg_prop)));
> > -	generate_irq_prop(fdt, dev->irq, IRQ_TYPE_LEVEL_HIGH);
> > +	irq_fn(fdt, dev->irq, IRQ_TYPE_LEVEL_HIGH);
> >  	_FDT(fdt_property_cell(fdt, "clock-frequency", 1843200));
> >  	_FDT(fdt_end_node(fdt));
> >  }
> > -#else
> > -#define serial8250_generate_fdt_node	NULL
> >  #endif
> >  
> >  static struct ioport_operations serial8250_ops = {
> >  	.io_in			= serial8250_in,
> >  	.io_out			= serial8250_out,
> > -	.generate_fdt_node	= serial8250_generate_fdt_node,
> >  };
> >  
> > -static int serial8250__device_init(struct kvm *kvm, struct serial8250_device *dev)
> > +static int serial8250__device_init(struct kvm *kvm,
> > +				   struct serial8250_device *dev)
> >  {
> >  	int r;
> >  
> > +	r = device__register(&dev->dev_hdr);
> > +	if (r < 0)
> > +		return r;
> > +
> >  	ioport__map_irq(&dev->irq);
> >  	r = ioport__register(kvm, dev->iobase, &serial8250_ops, 8, dev);  
> 
> It's unfortunate that we now create two devices for one serial instance: one here,
> and one created by ioport__register(). But I guess that's unavoidable in this
> patch, and later patches will remove it.

Well, we do this already, wherever we register multiple I/O ports per
device, RTC and i8042 are an example (because we register one device
per I/O port). This really isn't a particular problem, it's just ugly,
so just get's a tiny bit more uglier for a few patches that
hopefully nobody will actually use (in anger).

> 
> >  
> > @@ -438,6 +465,7 @@ cleanup:
> >  		struct serial8250_device *dev = &devices[j];
> >  
> >  		ioport__unregister(kvm, dev->iobase);
> > +		device__unregister(&dev->dev_hdr);
> >  	}
> >  
> >  	return r;
> > @@ -455,6 +483,7 @@ int serial8250__exit(struct kvm *kvm)
> >  		r = ioport__unregister(kvm, dev->iobase);
> >  		if (r < 0)
> >  			return r;
> > +		device__unregister(&dev->dev_hdr);
> >  	}
> >  
> >  	return 0;
> > diff --git a/include/kvm/kvm.h b/include/kvm/kvm.h
> > index 53373b08..ee99c28e 100644
> > --- a/include/kvm/kvm.h
> > +++ b/include/kvm/kvm.h
> > @@ -31,6 +31,8 @@
> >  	.name = #ext,			\
> >  	.code = ext
> >  
> > +typedef void (*fdt_irq_fn)(void *fdt, u8 irq, enum irq_type);  
> 
> Shouldn't that last parameter be enum irq_type irq_type? Would you consider moving
> the typedef to include/kvm/fdt.h?

I think where I came from was that typedef's don't need parameter names,
just the type. But just having (void *, u8, enum irq_type) is really
hard to understand, so I added parameter names where this helps. "enum
irq_type irq_type" looks redundant, but I can certainly add this for
consistency.

> Other than the nitpicks above, the patch looks sound to me. I also did a quick
> test by running kvm-unit-tests:
> 
> Reviewed-by: Alexandru Elisei <alexandru.elisei@arm.com>

Thanks!

Andre

> 
> Thanks,
> Alex
> > +
> >  enum {
> >  	KVM_VMSTATE_RUNNING,
> >  	KVM_VMSTATE_PAUSED,  

_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

WARNING: multiple messages have this Message-ID (diff)
From: Andre Przywara <andre.przywara@arm.com>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: kvm@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
	Julien Thierry <julien.thierry.kdev@gmail.com>,
	Will Deacon <will@kernel.org>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH kvmtool 02/21] hw/serial: Use device abstraction for FDT generator function
Date: Thu, 11 Feb 2021 17:45:47 +0000	[thread overview]
Message-ID: <20210211174547.2bf5a5a0@slackpad.fritz.box> (raw)
In-Reply-To: <d0fbeccf-ecf6-5b53-c165-67a531e79e45@arm.com>

On Thu, 11 Feb 2021 12:05:35 +0000
Alexandru Elisei <alexandru.elisei@arm.com> wrote:

Hi,

> On 12/10/20 2:28 PM, Andre Przywara wrote:
> > At the moment we use the .generate_fdt_node member of the ioport ops
> > structure to store the function pointer for the FDT node generator
> > function. ioport__register() will then put a wrapper and this pointer
> > into the device header.
> > The serial device is the only device making use of this special ioport
> > feature, so let's move this over to using the device header directly.
> >
> > This will allow us to get rid of this .generate_fdt_node member in the
> > ops and simplify the code.
> >
> > Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> > ---
> >  hw/serial.c       | 49 +++++++++++++++++++++++++++++++++++++----------
> >  include/kvm/kvm.h |  2 ++
> >  2 files changed, 41 insertions(+), 10 deletions(-)
> >
> > diff --git a/hw/serial.c b/hw/serial.c
> > index 13c4663e..b0465d99 100644
> > --- a/hw/serial.c
> > +++ b/hw/serial.c
> > @@ -23,6 +23,7 @@
> >  #define UART_IIR_TYPE_BITS	0xc0
> >  
> >  struct serial8250_device {
> > +	struct device_header	dev_hdr;
> >  	struct mutex		mutex;
> >  	u8			id;
> >  
> > @@ -53,9 +54,20 @@ struct serial8250_device {
> >  	.msr			= UART_MSR_DCD | UART_MSR_DSR | UART_MSR_CTS, \
> >  	.mcr			= UART_MCR_OUT2,
> >  
> > +#ifdef CONFIG_HAS_LIBFDT
> > +static
> > +void serial8250_generate_fdt_node(void *fdt, struct device_header *dev_hdr,
> > +				  fdt_irq_fn irq_fn);
> > +#else
> > +#define serial8250_generate_fdt_node	NULL
> > +#endif
> >  static struct serial8250_device devices[] = {
> >  	/* ttyS0 */
> >  	[0]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 0,
> > @@ -66,6 +78,10 @@ static struct serial8250_device devices[] = {
> >  	},
> >  	/* ttyS1 */
> >  	[1]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 1,
> > @@ -76,6 +92,10 @@ static struct serial8250_device devices[] = {
> >  	},
> >  	/* ttyS2 */
> >  	[2]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 2,
> > @@ -86,6 +106,10 @@ static struct serial8250_device devices[] = {
> >  	},
> >  	/* ttyS3 */
> >  	[3]	= {
> > +		.dev_hdr = {
> > +			.bus_type	= DEVICE_BUS_IOPORT,
> > +			.data		= serial8250_generate_fdt_node,
> > +		},
> >  		.mutex			= MUTEX_INITIALIZER,
> >  
> >  		.id			= 3,
> > @@ -371,13 +395,14 @@ char *fdt_stdout_path = NULL;
> >  
> >  #define DEVICE_NAME_MAX_LEN 32
> >  static
> > -void serial8250_generate_fdt_node(struct ioport *ioport, void *fdt,
> > -				  void (*generate_irq_prop)(void *fdt,
> > -							    u8 irq,
> > -							    enum irq_type))
> > +void serial8250_generate_fdt_node(void *fdt, struct device_header *dev_hdr,
> > +				  fdt_irq_fn irq_fn)
> >  {
> >  	char dev_name[DEVICE_NAME_MAX_LEN];
> > -	struct serial8250_device *dev = ioport->priv;
> > +	struct serial8250_device *dev = container_of(dev_hdr,
> > +						     struct serial8250_device,
> > +						     dev_hdr);
> > +
> >  	u64 addr = KVM_IOPORT_AREA + dev->iobase;
> >  	u64 reg_prop[] = {
> >  		cpu_to_fdt64(addr),
> > @@ -395,24 +420,26 @@ void serial8250_generate_fdt_node(struct ioport *ioport, void *fdt,
> >  	_FDT(fdt_begin_node(fdt, dev_name));
> >  	_FDT(fdt_property_string(fdt, "compatible", "ns16550a"));
> >  	_FDT(fdt_property(fdt, "reg", reg_prop, sizeof(reg_prop)));
> > -	generate_irq_prop(fdt, dev->irq, IRQ_TYPE_LEVEL_HIGH);
> > +	irq_fn(fdt, dev->irq, IRQ_TYPE_LEVEL_HIGH);
> >  	_FDT(fdt_property_cell(fdt, "clock-frequency", 1843200));
> >  	_FDT(fdt_end_node(fdt));
> >  }
> > -#else
> > -#define serial8250_generate_fdt_node	NULL
> >  #endif
> >  
> >  static struct ioport_operations serial8250_ops = {
> >  	.io_in			= serial8250_in,
> >  	.io_out			= serial8250_out,
> > -	.generate_fdt_node	= serial8250_generate_fdt_node,
> >  };
> >  
> > -static int serial8250__device_init(struct kvm *kvm, struct serial8250_device *dev)
> > +static int serial8250__device_init(struct kvm *kvm,
> > +				   struct serial8250_device *dev)
> >  {
> >  	int r;
> >  
> > +	r = device__register(&dev->dev_hdr);
> > +	if (r < 0)
> > +		return r;
> > +
> >  	ioport__map_irq(&dev->irq);
> >  	r = ioport__register(kvm, dev->iobase, &serial8250_ops, 8, dev);  
> 
> It's unfortunate that we now create two devices for one serial instance: one here,
> and one created by ioport__register(). But I guess that's unavoidable in this
> patch, and later patches will remove it.

Well, we do this already, wherever we register multiple I/O ports per
device, RTC and i8042 are an example (because we register one device
per I/O port). This really isn't a particular problem, it's just ugly,
so just get's a tiny bit more uglier for a few patches that
hopefully nobody will actually use (in anger).

> 
> >  
> > @@ -438,6 +465,7 @@ cleanup:
> >  		struct serial8250_device *dev = &devices[j];
> >  
> >  		ioport__unregister(kvm, dev->iobase);
> > +		device__unregister(&dev->dev_hdr);
> >  	}
> >  
> >  	return r;
> > @@ -455,6 +483,7 @@ int serial8250__exit(struct kvm *kvm)
> >  		r = ioport__unregister(kvm, dev->iobase);
> >  		if (r < 0)
> >  			return r;
> > +		device__unregister(&dev->dev_hdr);
> >  	}
> >  
> >  	return 0;
> > diff --git a/include/kvm/kvm.h b/include/kvm/kvm.h
> > index 53373b08..ee99c28e 100644
> > --- a/include/kvm/kvm.h
> > +++ b/include/kvm/kvm.h
> > @@ -31,6 +31,8 @@
> >  	.name = #ext,			\
> >  	.code = ext
> >  
> > +typedef void (*fdt_irq_fn)(void *fdt, u8 irq, enum irq_type);  
> 
> Shouldn't that last parameter be enum irq_type irq_type? Would you consider moving
> the typedef to include/kvm/fdt.h?

I think where I came from was that typedef's don't need parameter names,
just the type. But just having (void *, u8, enum irq_type) is really
hard to understand, so I added parameter names where this helps. "enum
irq_type irq_type" looks redundant, but I can certainly add this for
consistency.

> Other than the nitpicks above, the patch looks sound to me. I also did a quick
> test by running kvm-unit-tests:
> 
> Reviewed-by: Alexandru Elisei <alexandru.elisei@arm.com>

Thanks!

Andre

> 
> Thanks,
> Alex
> > +
> >  enum {
> >  	KVM_VMSTATE_RUNNING,
> >  	KVM_VMSTATE_PAUSED,  


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-02-11 17:54 UTC|newest]

Thread overview: 216+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 14:28 [PATCH kvmtool 00/21] Unify I/O port and MMIO trap handling Andre Przywara
2020-12-10 14:28 ` Andre Przywara
2020-12-10 14:28 ` Andre Przywara
2020-12-10 14:28 ` [PATCH kvmtool 01/21] ioport: Remove ioport__setup_arch() Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-10 17:44   ` Alexandru Elisei
2021-02-10 17:44     ` Alexandru Elisei
2021-02-10 17:44     ` Alexandru Elisei
2021-02-11 17:16     ` Andre Przywara
2021-02-11 17:16       ` Andre Przywara
2021-02-11 17:16       ` Andre Przywara
2021-02-11 17:32       ` Alexandru Elisei
2021-02-11 17:32         ` Alexandru Elisei
2021-02-11 17:32         ` Alexandru Elisei
2021-02-17 16:46         ` Andre Przywara
2021-02-17 16:46           ` Andre Przywara
2021-02-17 16:46           ` Andre Przywara
2021-02-22 10:23           ` Andre Przywara
2021-02-22 10:23             ` Andre Przywara
2021-02-22 10:23             ` Andre Przywara
2021-02-22 15:01             ` Alexandru Elisei
2021-02-22 15:01               ` Alexandru Elisei
2021-02-22 15:01               ` Alexandru Elisei
2020-12-10 14:28 ` [PATCH kvmtool 02/21] hw/serial: Use device abstraction for FDT generator function Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-11 12:05   ` Alexandru Elisei
2021-02-11 12:05     ` Alexandru Elisei
2021-02-11 12:05     ` Alexandru Elisei
2021-02-11 17:45     ` Andre Przywara [this message]
2021-02-11 17:45       ` Andre Przywara
2021-02-11 17:45       ` Andre Przywara
2020-12-10 14:28 ` [PATCH kvmtool 03/21] ioport: Retire .generate_fdt_node functionality Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-11 14:05   ` Alexandru Elisei
2021-02-11 14:05     ` Alexandru Elisei
2021-02-11 14:05     ` Alexandru Elisei
2021-02-17 15:54     ` Andre Przywara
2021-02-17 15:54       ` Andre Przywara
2021-02-17 15:54       ` Andre Przywara
2021-02-17 16:06       ` Alexandru Elisei
2021-02-17 16:06         ` Alexandru Elisei
2021-02-17 16:06         ` Alexandru Elisei
2020-12-10 14:28 ` [PATCH kvmtool 04/21] mmio: Extend handling to include ioport emulation Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-11 16:10   ` Alexandru Elisei
2021-02-11 16:10     ` Alexandru Elisei
2021-02-11 16:10     ` Alexandru Elisei
2021-02-17 17:43     ` Andre Przywara
2021-02-17 17:43       ` Andre Przywara
2021-02-17 17:43       ` Andre Przywara
2021-02-22 15:50       ` Alexandru Elisei
2021-02-22 15:50         ` Alexandru Elisei
2021-02-22 15:50         ` Alexandru Elisei
2020-12-10 14:28 ` [PATCH kvmtool 05/21] hw/i8042: Clean up data types Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-11 16:55   ` Alexandru Elisei
2021-02-11 16:55     ` Alexandru Elisei
2021-02-11 16:55     ` Alexandru Elisei
2021-02-17 17:46     ` Andre Przywara
2021-02-17 17:46       ` Andre Przywara
2021-02-17 17:46       ` Andre Przywara
2020-12-10 14:28 ` [PATCH kvmtool 06/21] hw/i8042: Refactor trap handler Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-11 17:23   ` Alexandru Elisei
2021-02-11 17:23     ` Alexandru Elisei
2021-02-11 17:23     ` Alexandru Elisei
2021-02-18 10:34     ` Andre Przywara
2021-02-18 10:34       ` Andre Przywara
2021-02-18 10:34       ` Andre Przywara
2021-02-18 11:17       ` Alexandru Elisei
2021-02-18 11:17         ` Alexandru Elisei
2021-02-18 11:17         ` Alexandru Elisei
2021-02-18 11:48         ` Andre Przywara
2021-02-18 11:48           ` Andre Przywara
2021-02-18 11:48           ` Andre Przywara
2021-02-22 16:03           ` Alexandru Elisei
2021-02-22 16:03             ` Alexandru Elisei
2021-02-22 16:03             ` Alexandru Elisei
2020-12-10 14:28 ` [PATCH kvmtool 07/21] hw/i8042: Switch to new trap handlers Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-12 10:41   ` Alexandru Elisei
2021-02-12 10:41     ` Alexandru Elisei
2021-02-12 10:41     ` Alexandru Elisei
2021-02-18 12:09     ` Andre Przywara
2021-02-18 12:09       ` Andre Przywara
2021-02-18 12:09       ` Andre Przywara
2021-02-22 16:19       ` Alexandru Elisei
2021-02-22 16:19         ` Alexandru Elisei
2021-02-22 16:19         ` Alexandru Elisei
2020-12-10 14:28 ` [PATCH kvmtool 08/21] x86/ioport: Refactor " Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-12 11:14   ` Alexandru Elisei
2021-02-12 11:14     ` Alexandru Elisei
2021-02-12 11:14     ` Alexandru Elisei
2020-12-10 14:28 ` [PATCH kvmtool 09/21] x86/ioport: Switch to new " Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-12 11:27   ` Alexandru Elisei
2021-02-12 11:27     ` Alexandru Elisei
2021-02-12 11:27     ` Alexandru Elisei
2021-02-18 14:05     ` Andre Przywara
2021-02-18 14:05       ` Andre Przywara
2021-02-18 14:05       ` Andre Przywara
2020-12-10 14:28 ` [PATCH kvmtool 10/21] hw/rtc: Refactor " Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-12 11:56   ` Alexandru Elisei
2021-02-12 11:56     ` Alexandru Elisei
2021-02-12 11:56     ` Alexandru Elisei
2020-12-10 14:28 ` [PATCH kvmtool 11/21] hw/rtc: Switch to new trap handler Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-12 12:02   ` Alexandru Elisei
2021-02-12 12:02     ` Alexandru Elisei
2021-02-12 12:02     ` Alexandru Elisei
2020-12-10 14:28 ` [PATCH kvmtool 12/21] hw/vesa: Switch trap handling to use MMIO handler Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2020-12-10 14:28   ` Andre Przywara
2021-02-12 17:50   ` Alexandru Elisei
2021-02-12 17:50     ` Alexandru Elisei
2021-02-12 17:50     ` Alexandru Elisei
2020-12-10 14:29 ` [PATCH kvmtool 13/21] hw/serial: Refactor trap handler Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2021-02-16 14:22   ` Alexandru Elisei
2021-02-16 14:22     ` Alexandru Elisei
2021-02-16 14:22     ` Alexandru Elisei
2021-02-18 14:41     ` Andre Przywara
2021-02-18 14:41       ` Andre Przywara
2021-02-18 14:41       ` Andre Przywara
2021-02-22 17:40       ` Alexandru Elisei
2021-02-22 17:40         ` Alexandru Elisei
2021-02-22 17:40         ` Alexandru Elisei
2021-02-24 14:54         ` Andre Przywara
2021-02-24 14:54           ` Andre Przywara
2021-02-24 14:54           ` Andre Przywara
2020-12-10 14:29 ` [PATCH kvmtool 14/21] hw/serial: Switch to new trap handlers Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2021-02-16 14:31   ` Alexandru Elisei
2021-02-16 14:31     ` Alexandru Elisei
2021-02-16 14:31     ` Alexandru Elisei
2020-12-10 14:29 ` [PATCH kvmtool 15/21] vfio: Refactor ioport trap handler Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2021-02-16 14:47   ` Alexandru Elisei
2021-02-16 14:47     ` Alexandru Elisei
2021-02-16 14:47     ` Alexandru Elisei
2021-02-18 15:51     ` Andre Przywara
2021-02-18 15:51       ` Andre Przywara
2021-02-18 15:51       ` Andre Przywara
2020-12-10 14:29 ` [PATCH kvmtool 16/21] vfio: Switch to new ioport trap handlers Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2021-02-16 14:52   ` Alexandru Elisei
2021-02-16 14:52     ` Alexandru Elisei
2021-02-16 14:52     ` Alexandru Elisei
2020-12-10 14:29 ` [PATCH kvmtool 17/21] virtio: Switch trap handling to use MMIO handler Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2021-02-16 17:03   ` Alexandru Elisei
2021-02-16 17:03     ` Alexandru Elisei
2021-02-16 17:03     ` Alexandru Elisei
2021-02-18 16:13     ` Andre Przywara
2021-02-18 16:13       ` Andre Przywara
2021-02-18 16:13       ` Andre Przywara
2020-12-10 14:29 ` [PATCH kvmtool 18/21] pci: " Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2021-02-17 15:14   ` Alexandru Elisei
2021-02-17 15:14     ` Alexandru Elisei
2021-02-17 15:14     ` Alexandru Elisei
2020-12-10 14:29 ` [PATCH kvmtool 19/21] Remove ioport specific routines Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2021-02-17 15:49   ` Alexandru Elisei
2021-02-17 15:49     ` Alexandru Elisei
2021-02-17 15:49     ` Alexandru Elisei
2021-02-17 16:11     ` Alexandru Elisei
2021-02-17 16:11       ` Alexandru Elisei
2021-02-17 16:11       ` Alexandru Elisei
2021-02-18 16:34       ` Andre Przywara
2021-02-18 16:34         ` Andre Przywara
2021-02-18 16:34         ` Andre Przywara
2020-12-10 14:29 ` [PATCH kvmtool 20/21] hw/serial: ARM/arm64: Use MMIO at higher addresses Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2021-02-17 16:48   ` Alexandru Elisei
2021-02-17 16:48     ` Alexandru Elisei
2021-02-17 16:48     ` Alexandru Elisei
2021-02-18 12:18     ` Alexandru Elisei
2021-02-18 12:18       ` Alexandru Elisei
2021-02-18 12:18       ` Alexandru Elisei
2021-02-18 16:38       ` Andre Przywara
2021-02-18 16:38         ` Andre Przywara
2021-02-18 16:38         ` Andre Przywara
2020-12-10 14:29 ` [PATCH kvmtool 21/21] hw/rtc: " Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2020-12-10 14:29   ` Andre Przywara
2021-02-18 13:33   ` Alexandru Elisei
2021-02-18 13:33     ` Alexandru Elisei
2021-02-18 13:33     ` Alexandru Elisei
2021-02-18 16:41     ` Andre Przywara
2021-02-18 16:41       ` Andre Przywara
2021-02-18 16:41       ` Andre Przywara
2021-02-10 17:44 ` [PATCH kvmtool 00/21] Unify I/O port and MMIO trap handling Alexandru Elisei
2021-02-10 17:44   ` Alexandru Elisei
2021-02-10 17:44   ` Alexandru Elisei

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=20210211174547.2bf5a5a0@slackpad.fritz.box \
    --to=andre.przywara@arm.com \
    --cc=alexandru.elisei@arm.com \
    --cc=julien.thierry.kdev@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=will@kernel.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.