mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] tools: include: sync include/api/linux/kvm.h
Date: Sat, 22 Oct 2022 13:53:45 +0200	[thread overview]
Message-ID: <e436fc94-6bd7-989d-a1bb-5cd08a7d10c3@redhat.com> (raw)
In-Reply-To: <87bkq4gjwc.wl-maz@kernel.org>

On 10/22/22 13:47, Marc Zyngier wrote:
>> Provide a definition of KVM_CAP_DIRTY_LOG_RING_ACQ_REL.
>>
>> Fixes: 4b3402f1f4d9 ("KVM: selftests: dirty-log: Use KVM_CAP_DIRTY_LOG_RING_ACQ_REL if available")
>> Cc: Marc Zyngier<maz@kernel.org>
>> Signed-off-by: Paolo Bonzini<pbonzini@redhat.com>
>> ---
>>   tools/include/uapi/linux/kvm.h | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/tools/include/uapi/linux/kvm.h b/tools/include/uapi/linux/kvm.h
>> index eed0315a77a6..0d5d4419139a 100644
>> --- a/tools/include/uapi/linux/kvm.h
>> +++ b/tools/include/uapi/linux/kvm.h
>> @@ -1177,6 +1177,7 @@ struct kvm_ppc_resize_hpt {
>>   #define KVM_CAP_VM_DISABLE_NX_HUGE_PAGES 220
>>   #define KVM_CAP_S390_ZPCI_OP 221
>>   #define KVM_CAP_S390_CPU_TOPOLOGY 222
>> +#define KVM_CAP_DIRTY_LOG_RING_ACQ_REL 223
>>   
>>   #ifdef KVM_CAP_IRQ_ROUTING
>>   
> Huh, I wonder how I missed that one, as the test were compiling here.
> 
> Acked-by: Marc Zyngier<maz@kernel.org>

5 minutes later -- The tests do not use that file, they use usr/include/ 
in the build tree.  So the right Fixes tag is 17601bfed909 ("KVM: Add 
KVM_CAP_DIRTY_LOG_RING_ACQ_REL capability and config option").

Paolo


      reply	other threads:[~2022-10-22 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 11:44 Paolo Bonzini
2022-10-22 11:47 ` Marc Zyngier
2022-10-22 11:53   ` Paolo Bonzini [this message]

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=e436fc94-6bd7-989d-a1bb-5cd08a7d10c3@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®