linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm64: ITS: return 1 on successful MSI injection
Date: Tue, 2 Aug 2016 13:28:44 +0100	[thread overview]
Message-ID: <57A091FC.9070607@arm.com> (raw)
In-Reply-To: <20160802122309.GH32244@cbox>

On 02/08/16 13:23, Christoffer Dall wrote:
> On Tue, Aug 02, 2016 at 12:10:58PM +0100, Andre Przywara wrote:
>> According to the KVM API documentation a successful MSI injection
>> should return a value > 0 on success.
>> Since we pass the return value of vgic_its_inject_msi() directly on
>> to upper layers and userland, we need to use the same semantics here.
>> Briefly tested with QEMU and kvmtool on GICv3 hardware and the model.
>>
>> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
>> ---
>> Applies on top of next-20160728. Let me know if I should use a
>> different base.
>>
>> Cheers,
>> Andre.
>>
>>  virt/kvm/arm/vgic/vgic-its.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/virt/kvm/arm/vgic/vgic-its.c b/virt/kvm/arm/vgic/vgic-its.c
>> index 07411cf..3268250 100644
>> --- a/virt/kvm/arm/vgic/vgic-its.c
>> +++ b/virt/kvm/arm/vgic/vgic-its.c
>> @@ -468,6 +468,7 @@ static void vgic_its_trigger_msi(struct kvm *kvm, struct vgic_its *its,
>>   * Queries the KVM IO bus framework to get the ITS pointer from the given
>>   * doorbell address.
>>   * We then call vgic_its_trigger_msi() with the decoded data.
>> + * According to the KVM_SIGNAL_MSI API description returns > 0 on success.
>>   */
>>  int vgic_its_inject_msi(struct kvm *kvm, struct kvm_msi *msi)
>>  {
>> @@ -493,7 +494,7 @@ int vgic_its_inject_msi(struct kvm *kvm, struct kvm_msi *msi)
>>  	vgic_its_trigger_msi(kvm, iodev->its, msi->devid, msi->data);
>>  	mutex_unlock(&iodev->its->its_lock);
>>  
>> -	return 0;
>> +	return 1;
>>  }
>>  
>>  /* Requires the its_lock to be held. */
> 
> Do we have a clear understanding of what 'guest blocked the MSI'
> constitutes in the ARM world?

I would define it as "the guest has not configured the ITS so that the
corresponding LPI could be successfully delivered". Which is any of the
conditions where the interrupt cannot make it into the pending table,
and is dropped on the floor.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2016-08-02 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 11:10 [PATCH] KVM: arm64: ITS: return 1 on successful MSI injection Andre Przywara
2016-08-02 11:45 ` Marc Zyngier
2016-08-02 12:23 ` Christoffer Dall
2016-08-02 12:28   ` Marc Zyngier [this message]
2016-08-02 13:57     ` Christoffer Dall

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=57A091FC.9070607@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).