public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jon Doron <arilou@gmail.com>
Cc: kvm@vger.kernel.org, linux-hyperv@vger.kernel.org,
	Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [PATCH v2 1/4] x86/kvm/hyper-v: Align the hcall param for kvm_hyperv_exit
Date: Thu, 5 Mar 2020 16:29:45 +0100	[thread overview]
Message-ID: <0edfee0e-01ee-bb62-5fc5-67d7d45ec192@redhat.com> (raw)
In-Reply-To: <CAP7QCoj9=mZCWdiOa92QP9Fjb=p3DfKTs0xHKZYQ+yRiMabmLA@mail.gmail.com>

On 05/03/20 15:53, Jon Doron wrote:
> Vitaly recommended we will align the struct to 64bit...

Oh, then I think you actually should add a padding after "__u32 type;"
and "__u32 msr;" if you want to make it explicit.  The patch, as is, is
not aligning anything, hence my confusion.

Thanks,

Paolo

> On Thu, Mar 5, 2020 at 4:24 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> On 05/03/20 15:01, Jon Doron wrote:
>>> Signed-off-by: Jon Doron <arilou@gmail.com>
>>> ---
>>>  include/uapi/linux/kvm.h | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
>>> index 4b95f9a31a2f..9b4d449f4d20 100644
>>> --- a/include/uapi/linux/kvm.h
>>> +++ b/include/uapi/linux/kvm.h
>>> @@ -200,6 +200,7 @@ struct kvm_hyperv_exit {
>>>                       __u64 input;
>>>                       __u64 result;
>>>                       __u64 params[2];
>>> +                     __u32 pad;
>>>               } hcall;
>>>       } u;
>>>  };
>>>
>>
>> Can you explain the purpose of this patch?
>>
>> Paolo
>>
> 


  reply	other threads:[~2020-03-05 15:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 14:01 [PATCH v2 0/4] x86/kvm/hyper-v: add support for synthetic debugger Jon Doron
2020-03-05 14:01 ` [PATCH v2 1/4] x86/kvm/hyper-v: Align the hcall param for kvm_hyperv_exit Jon Doron
2020-03-05 14:23   ` Paolo Bonzini
2020-03-05 14:53     ` Jon Doron
2020-03-05 15:29       ` Paolo Bonzini [this message]
2020-03-05 15:52         ` Jon Doron
2020-03-05 16:45           ` Paolo Bonzini
     [not found]         ` <87ftelepwz.fsf@vitty.brq.redhat.com>
2020-03-06 14:42           ` Jon Doron
2020-03-05 14:01 ` [PATCH v2 2/4] x86/kvm/hyper-v: Add support for synthetic debugger capability Jon Doron
2020-03-06 15:26   ` Vitaly Kuznetsov
2020-03-06 15:45     ` Michael Kelley
2020-03-06 16:34     ` Jon Doron
2020-03-05 14:01 ` [PATCH v2 3/4] x86/kvm/hyper-v: enable hypercalls regardless of hypercall page Jon Doron
2020-03-05 14:01 ` [PATCH v2 4/4] x86/kvm/hyper-v: Add support for synthetic debugger via hypercalls Jon Doron
     [not found]   ` <871rq5ebnx.fsf@vitty.brq.redhat.com>
2020-03-06 16:36     ` Jon Doron

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=0edfee0e-01ee-bb62-5fc5-67d7d45ec192@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arilou@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=vkuznets@redhat.com \
    /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