All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Xu <xuwei5@hisilicon.com>
To: Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	<xen-devel@lists.xenproject.org>
Cc: prime.zeng@hisilicon.com, shameerali.kolothum.thodi@huawei.com,
	linuxarm@huawei.com
Subject: Re: [Xen-devel] [PATCH] xen/arm: vgic-v3: Fix the typo of GICD IRQ active status range
Date: Sat, 28 Dec 2019 16:57:52 +0800	[thread overview]
Message-ID: <5E071910.2070002@hisilicon.com> (raw)
In-Reply-To: <e96ddb84-db96-5316-05a7-632fed7dddb8@xen.org>

Hi Julien,

On 2019/12/28 16:09, Julien Grall wrote:
> Hi,
>
> On 28/12/2019 03:08, Wei Xu wrote:
>> This patch fixes the typo about the active status range of an IRQ
>> via GICD. Otherwise it will be failed to handle the mmio access and
>> inject a data abort.
> I have seen a patch similar from NXP a month ago and I disagreed on 
> the approach.
>
> If you look at the context you modifed, it says that reading ACTIVER 
> is not supported. While I agree the behavior is not consistent accross 
> ACTIVER, injecting a data abort is a perfectly fine behavior to me 
> (though not spec compliant) as we don't implement the registers 
> correctly.
>
> I guess you are sending this patch, because you tried Linux 5.4 (or 
> later) on Xen, right? Linux has recently began to read ACTIVER to 
> check whether an IRQ is active at the HW level during the 
> synchronizing of the IRQS. From my understanding, this is used because 
> there is a window where the interrupt is active at the HW level but 
> the Linux IRQ subsystem is not aware of it.
>
> While the patch below will allow Linux 5.4 to not crash, it is not 
> going to make it fly very far because of the above. So I am rather not 
> happy with persuing with returning 0.
>

Yes, I am using Linux 5.5-rc2 :)
Got it and thanks for the explanation.
I am not insistent on this and OK to wait for the update.
Thanks and have a very happy new year!

Best Regards,
Wei

> @Stefano, you mention you will look at implementing ACTIVER. What's 
> the state?
>
> >
>> Fixes: a2b83f95bfad ("xen/arm: vgic: Properly emulate the full 
>> register")
>>
>> Signed-off-by: Wei Xu <xuwei5@hisilicon.com>
>> ---
>>   xen/arch/arm/vgic-v3.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/xen/arch/arm/vgic-v3.c b/xen/arch/arm/vgic-v3.c
>> index 422b94f..e802f20 100644
>> --- a/xen/arch/arm/vgic-v3.c
>> +++ b/xen/arch/arm/vgic-v3.c
>> @@ -706,7 +706,7 @@ static int __vgic_v3_distr_common_mmio_read(const 
>> char *name, struct vcpu *v,
>>           goto read_as_zero;
>>         /* Read the active status of an IRQ via GICD/GICR is not 
>> supported */
>> -    case VRANGE32(GICD_ISACTIVER, GICD_ISACTIVER):
>> +    case VRANGE32(GICD_ISACTIVER, GICD_ISACTIVERN):
>>       case VRANGE32(GICD_ICACTIVER, GICD_ICACTIVERN):
>>           goto read_as_zero;
>>
>
> Cheers,
>



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-12-28  8:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-28  2:08 [Xen-devel] [PATCH] xen/arm: vgic-v3: Fix the typo of GICD IRQ active status range Wei Xu
2019-12-28  8:09 ` Julien Grall
2019-12-28  8:57   ` Wei Xu [this message]
2020-01-06 22:01     ` Stefano Stabellini
2020-01-07  8:39       ` Wei Xu
2020-01-07  9:10         ` Julien Grall
2020-01-07  9:28           ` Wei Xu
2020-01-07 10:51             ` Julien Grall
2020-01-07 10:56               ` Wei Xu
2020-01-07 11:13                 ` Julien Grall
2020-01-07 11:45                   ` Wei Xu
2020-01-07  9:48           ` Wei Xu
2020-01-07 11:42             ` Julien Grall
2020-01-07 12:55               ` Wei Xu
2020-01-07 15:12                 ` Julien Grall
2020-01-17  9:06                   ` Wei Xu
2020-01-17 20:41                     ` [Xen-devel] Interaction between ACPI and dt_unreserved_regions() (WAS: Re: [PATCH] xen/arm: vgic-v3: Fix the typo of GICD IRQ active status range) Julien Grall
2020-01-20  4:05                       ` Wei Xu

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=5E071910.2070002@hisilicon.com \
    --to=xuwei5@hisilicon.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=julien@xen.org \
    --cc=linuxarm@huawei.com \
    --cc=prime.zeng@hisilicon.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=sstabellini@kernel.org \
    --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.