From: Joao Martins <joao.m.martins@oracle.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
kvm list <kvm@vger.kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Radim Krcmar <rkrcmar@redhat.com>
Subject: Re: [PATCH v1 3/3] MAINTAINERS: xen, kvm: track pvclock-abi.h changes
Date: Thu, 26 Jan 2017 20:08:43 +0000 [thread overview]
Message-ID: <588A574B.1090803@oracle.com> (raw)
In-Reply-To: <CALCETrVVBBXnCjHYX95FnPuNdepVa1pCthP59sWwndVG6jzE2w@mail.gmail.com>
On 01/26/2017 05:25 PM, Andy Lutomirski wrote:
> On Wed, Jan 25, 2017 at 9:33 AM, Joao Martins <joao.m.martins@oracle.com> wrote:
>> This file defines an ABI shared between guest and hypervisor(s)
>> (KVM, Xen) and as such there should be an correspondent entry in
>> MAINTAINERS file. Notice that there's already a text notice at the
>> top of the header file, hence this commit simply enforces it more
>> explicitly and have both peers noticed when such changes happen.
>>
>> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
>> ---
>> This was suggested by folks at xen-devel as we missed some of the
>> ABI additions (e.g. flags field in pvti, TSC stable bit) - so this
>> patch is to help preventing that from happening. Alternatively I
>> could instead add a "PVCLOCK ABI" section in this file with the
>> two mailing lists.
>
> If you do the latter, please add me as an R:.
OK, Thanks.
Since the ABI is used on both hypervisors I'll leave/wait for maintainers to
voice their preference.
Joao
next prev parent reply other threads:[~2017-01-26 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 17:33 [PATCH v1 0/3] x86/xen: pvclock vdso support Joao Martins
2017-01-25 17:33 ` [PATCH v1 1/3] x86/pvclock: add setter for pvclock_pvti_cpu0_va Joao Martins
2017-01-26 17:25 ` Andy Lutomirski
2017-01-26 17:25 ` Andy Lutomirski
2017-01-26 19:58 ` Joao Martins
2017-01-25 17:33 ` [PATCH v1 2/3] x86/xen/time: setup vcpu 0 time info page Joao Martins
2017-01-25 19:26 ` Boris Ostrovsky
2017-01-26 13:22 ` Joao Martins
2017-01-26 17:18 ` Andy Lutomirski
2017-01-25 17:33 ` [PATCH v1 3/3] MAINTAINERS: xen, kvm: track pvclock-abi.h changes Joao Martins
2017-01-26 17:25 ` Andy Lutomirski
2017-01-26 20:08 ` Joao Martins [this message]
2017-01-27 14:54 ` Juergen Gross
2017-01-27 14:54 ` Juergen Gross
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=588A574B.1090803@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--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.