All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: al.stone@linaro.org, kvm@vger.kernel.org, marc.zyngier@arm.com,
	Jason Cooper <jason@lakedaemon.net>,
	linux-kernel@vger.kernel.org, fu.wei@linaro.org,
	Thomas Gleixner <tglx@linutronix.de>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org, gg@slimlogic.co.uk
Subject: Re: [PATCH v4 6/9] irqchip/gic-v3: Parse and export virtual GIC information
Date: Mon, 4 Apr 2016 10:14:38 +0100	[thread overview]
Message-ID: <5702307E.2020304@arm.com> (raw)
In-Reply-To: <20160401101308.GB20224@cbox>

Hi Christoffer,

On 01/04/2016 11:13, Christoffer Dall wrote:
> On Thu, Mar 24, 2016 at 05:53:40PM +0000, Julien Grall wrote:
>> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
>> index 50e87e6..b5ed8be 100644
>> --- a/drivers/irqchip/irq-gic-v3.c
>> +++ b/drivers/irqchip/irq-gic-v3.c

[...]

>> @@ -901,6 +904,39 @@ static int __init gic_validate_dist_version(void __iomem *dist_base)
>>   	return 0;
>>   }
>>
>> +static void __init gic_of_setup_kvm_info(struct device_node *node)
>> +{
>> +	int ret;
>> +	struct resource r;
>> +	u32 gicv_idx;
>> +
>> +	gic_v3_kvm_info.type = GIC_V3;
>> +
>> +	gic_v3_kvm_info.maint_irq = irq_of_parse_and_map(node, 0);
>> +	if (!gic_v3_kvm_info.maint_irq)
>> +		return;
>> +
>> +	if (of_property_read_u32(node, "#redistributor-regions",
>> +				 &gicv_idx))
>> +		gicv_idx = 1;
>> +
>> +	gicv_idx += 3;	/* Also skip GICD, GICC, GICH */
>> +	ret = of_address_to_resource(node, gicv_idx, &r);
>> +	if (!ret) {
>> +		if (!PAGE_ALIGNED(r.start))
>> +			pr_warn("GICV physical address 0x%llx not page aligned\n",
>> +				(unsigned long long)r.start);
>> +		else if (!PAGE_ALIGNED(resource_size(&r)))
>> +			pr_warn("GICV size 0x%llx not a multiple of page size 0x%lx\n",
>> +				(unsigned long long)resource_size(&r),
>> +				PAGE_SIZE);
>> +		else
>
> it seems like you're also checking the above items in the KVM code
> itself, so I still don't understand why we have to do this twice.
>
> My feeling here is that you want to just lookup if you have the proper
> resources to fill in the struct in the GIC driver, and fill in the
> struct with data if the firmware gave you something.
>
> It's then up to KVM to deal with its constraints, such as the resources
> being page-aligned etc.  But I suppose you could also argue that the GIC
> code knows how this hardware resource can or cannot be used and
> therefore should check it.
>
> But in any case, I don't understand why we check it more than one place?

Sorry, I forgot to remove these checks when I re-introduced them in the 
KVM code.

I will remove them in the next version.

Regards,

-- 
Julien Grall

WARNING: multiple messages have this Message-ID (diff)
From: julien.grall@arm.com (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 6/9] irqchip/gic-v3: Parse and export virtual GIC information
Date: Mon, 4 Apr 2016 10:14:38 +0100	[thread overview]
Message-ID: <5702307E.2020304@arm.com> (raw)
In-Reply-To: <20160401101308.GB20224@cbox>

Hi Christoffer,

On 01/04/2016 11:13, Christoffer Dall wrote:
> On Thu, Mar 24, 2016 at 05:53:40PM +0000, Julien Grall wrote:
>> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
>> index 50e87e6..b5ed8be 100644
>> --- a/drivers/irqchip/irq-gic-v3.c
>> +++ b/drivers/irqchip/irq-gic-v3.c

[...]

>> @@ -901,6 +904,39 @@ static int __init gic_validate_dist_version(void __iomem *dist_base)
>>   	return 0;
>>   }
>>
>> +static void __init gic_of_setup_kvm_info(struct device_node *node)
>> +{
>> +	int ret;
>> +	struct resource r;
>> +	u32 gicv_idx;
>> +
>> +	gic_v3_kvm_info.type = GIC_V3;
>> +
>> +	gic_v3_kvm_info.maint_irq = irq_of_parse_and_map(node, 0);
>> +	if (!gic_v3_kvm_info.maint_irq)
>> +		return;
>> +
>> +	if (of_property_read_u32(node, "#redistributor-regions",
>> +				 &gicv_idx))
>> +		gicv_idx = 1;
>> +
>> +	gicv_idx += 3;	/* Also skip GICD, GICC, GICH */
>> +	ret = of_address_to_resource(node, gicv_idx, &r);
>> +	if (!ret) {
>> +		if (!PAGE_ALIGNED(r.start))
>> +			pr_warn("GICV physical address 0x%llx not page aligned\n",
>> +				(unsigned long long)r.start);
>> +		else if (!PAGE_ALIGNED(resource_size(&r)))
>> +			pr_warn("GICV size 0x%llx not a multiple of page size 0x%lx\n",
>> +				(unsigned long long)resource_size(&r),
>> +				PAGE_SIZE);
>> +		else
>
> it seems like you're also checking the above items in the KVM code
> itself, so I still don't understand why we have to do this twice.
>
> My feeling here is that you want to just lookup if you have the proper
> resources to fill in the struct in the GIC driver, and fill in the
> struct with data if the firmware gave you something.
>
> It's then up to KVM to deal with its constraints, such as the resources
> being page-aligned etc.  But I suppose you could also argue that the GIC
> code knows how this hardware resource can or cannot be used and
> therefore should check it.
>
> But in any case, I don't understand why we check it more than one place?

Sorry, I forgot to remove these checks when I re-introduced them in the 
KVM code.

I will remove them in the next version.

Regards,

-- 
Julien Grall

WARNING: multiple messages have this Message-ID (diff)
From: Julien Grall <julien.grall@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: kvmarm@lists.cs.columbia.edu, marc.zyngier@arm.com,
	fu.wei@linaro.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, wei@redhat.com,
	al.stone@linaro.org, gg@slimlogic.co.uk,
	Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH v4 6/9] irqchip/gic-v3: Parse and export virtual GIC information
Date: Mon, 4 Apr 2016 10:14:38 +0100	[thread overview]
Message-ID: <5702307E.2020304@arm.com> (raw)
In-Reply-To: <20160401101308.GB20224@cbox>

Hi Christoffer,

On 01/04/2016 11:13, Christoffer Dall wrote:
> On Thu, Mar 24, 2016 at 05:53:40PM +0000, Julien Grall wrote:
>> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
>> index 50e87e6..b5ed8be 100644
>> --- a/drivers/irqchip/irq-gic-v3.c
>> +++ b/drivers/irqchip/irq-gic-v3.c

[...]

>> @@ -901,6 +904,39 @@ static int __init gic_validate_dist_version(void __iomem *dist_base)
>>   	return 0;
>>   }
>>
>> +static void __init gic_of_setup_kvm_info(struct device_node *node)
>> +{
>> +	int ret;
>> +	struct resource r;
>> +	u32 gicv_idx;
>> +
>> +	gic_v3_kvm_info.type = GIC_V3;
>> +
>> +	gic_v3_kvm_info.maint_irq = irq_of_parse_and_map(node, 0);
>> +	if (!gic_v3_kvm_info.maint_irq)
>> +		return;
>> +
>> +	if (of_property_read_u32(node, "#redistributor-regions",
>> +				 &gicv_idx))
>> +		gicv_idx = 1;
>> +
>> +	gicv_idx += 3;	/* Also skip GICD, GICC, GICH */
>> +	ret = of_address_to_resource(node, gicv_idx, &r);
>> +	if (!ret) {
>> +		if (!PAGE_ALIGNED(r.start))
>> +			pr_warn("GICV physical address 0x%llx not page aligned\n",
>> +				(unsigned long long)r.start);
>> +		else if (!PAGE_ALIGNED(resource_size(&r)))
>> +			pr_warn("GICV size 0x%llx not a multiple of page size 0x%lx\n",
>> +				(unsigned long long)resource_size(&r),
>> +				PAGE_SIZE);
>> +		else
>
> it seems like you're also checking the above items in the KVM code
> itself, so I still don't understand why we have to do this twice.
>
> My feeling here is that you want to just lookup if you have the proper
> resources to fill in the struct in the GIC driver, and fill in the
> struct with data if the firmware gave you something.
>
> It's then up to KVM to deal with its constraints, such as the resources
> being page-aligned etc.  But I suppose you could also argue that the GIC
> code knows how this hardware resource can or cannot be used and
> therefore should check it.
>
> But in any case, I don't understand why we check it more than one place?

Sorry, I forgot to remove these checks when I re-introduced them in the 
KVM code.

I will remove them in the next version.

Regards,

-- 
Julien Grall

  parent reply	other threads:[~2016-04-04  9:13 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 17:53 [PATCH v4 0/9] arm64: Add support for KVM with ACPI Julien Grall
2016-03-24 17:53 ` Julien Grall
2016-03-24 17:53 ` [PATCH v4 1/9] clocksource: arm_arch_timer: Gather KVM specific information in a structure Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-29 17:13   ` Daniel Lezcano
2016-03-29 17:13     ` Daniel Lezcano
2016-03-29 17:13     ` Daniel Lezcano
2016-03-29 17:32     ` Marc Zyngier
2016-03-29 17:32       ` Marc Zyngier
2016-03-29 17:32       ` Marc Zyngier
2016-03-30  9:06       ` Christoffer Dall
2016-03-30  9:06         ` Christoffer Dall
2016-03-30  9:12         ` Marc Zyngier
2016-03-30  9:12           ` Marc Zyngier
2016-03-30  9:52           ` Daniel Lezcano
2016-03-30  9:52             ` Daniel Lezcano
2016-03-30  9:52             ` Daniel Lezcano
2016-03-24 17:53 ` [PATCH v4 2/9] clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get the virtual IRQ Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53 ` [PATCH v4 3/9] irqchip/gic-v2: Gather ACPI specific data in a single structure Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53 ` [PATCH v4 4/9] irqchip/gic-v2: Parse and export virtual GIC information Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53 ` [PATCH v4 5/9] irqchip/gic-v3: Gather all ACPI specific data in a single structure Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53 ` [PATCH v4 6/9] irqchip/gic-v3: Parse and export virtual GIC information Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-04-01 10:13   ` Christoffer Dall
2016-04-01 10:13     ` Christoffer Dall
2016-04-01 10:13     ` Christoffer Dall
2016-04-01 10:25     ` Marc Zyngier
2016-04-01 10:25       ` Marc Zyngier
2016-04-01 10:25       ` Marc Zyngier
2016-04-04  9:14     ` Julien Grall [this message]
2016-04-04  9:14       ` Julien Grall
2016-04-04  9:14       ` Julien Grall
2016-03-24 17:53 ` [PATCH v4 7/9] KVM: arm/arm64: arch_timer: Rely on the arch timer to parse the firmware tables Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53 ` [PATCH v4 8/9] KVM: arm/arm64: vgic: Rely on the GIC driver " Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-04-01 10:32   ` Christoffer Dall
2016-04-01 10:32     ` Christoffer Dall
2016-04-01 10:32     ` Christoffer Dall
2016-03-24 17:53 ` [PATCH v4 9/9] clocksource: arm_arch_timer: Remove arch_timer_get_timecounter Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-24 17:53   ` Julien Grall
2016-03-29 14:39   ` Daniel Lezcano
2016-03-29 14:39     ` Daniel Lezcano
2016-03-29 14:39     ` Daniel Lezcano
2016-03-29 16:04     ` Julien Grall
2016-03-29 16:04       ` Julien Grall

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=5702307E.2020304@arm.com \
    --to=julien.grall@arm.com \
    --cc=al.stone@linaro.org \
    --cc=christoffer.dall@linaro.org \
    --cc=fu.wei@linaro.org \
    --cc=gg@slimlogic.co.uk \
    --cc=jason@lakedaemon.net \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=tglx@linutronix.de \
    /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.