From: Tamas K Lengyel <tamas@tklengyel.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: wei.liu2@citrix.com, Keir Fraser <keir@xen.org>,
stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
Ian Jackson <ian.jackson@eu.citrix.com>,
julien.grall@arm.com, Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] vm_event: Implement ARM SMC events
Date: Tue, 12 Apr 2016 09:08:40 -0600 [thread overview]
Message-ID: <CABfawhmr1aG3pKZ0D9g6=KMzB1D5vtHg7jVivCm0J2TdWgc6Lg@mail.gmail.com> (raw)
In-Reply-To: <570C891E.5090904@bitdefender.com>
[-- Attachment #1.1: Type: text/plain, Size: 667 bytes --]
> >> @@ -254,6 +279,7 @@ typedef struct vm_event_st {
> > >union {
> > >union {
> > >struct vm_event_regs_x86 x86;
> >> + struct vm_event_regs_arm arm;
> > >} regs;
> >
> > Does this alter the x86 ABI? Perhaps the ARM structure is
small enough for
> > this to not happen now, but what's the general idea about not breaking
other
> > arch'es ABIs when adding support for a new arch here?
>
> I'd suggest modifying VM_EVENT_INTERFACE_VERSION whenever that becomes
> the case.
>
Yeap, that's what I had in mind too, if we end up changing the layout or
the size of the struct we will increment the version.
Tamas
[-- Attachment #1.2: Type: text/html, Size: 933 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-12 15:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 19:47 [PATCH] vm_event: Implement ARM SMC events Tamas K Lengyel
2016-04-12 4:31 ` Jan Beulich
2016-04-12 5:35 ` Razvan Cojocaru
2016-04-12 15:08 ` Tamas K Lengyel [this message]
2016-04-12 15:05 ` Tamas K Lengyel
2016-04-12 15:58 ` Julien Grall
2016-04-12 17:58 ` Tamas K Lengyel
2016-04-12 7:51 ` Corneliu ZUZU
2016-04-12 15:01 ` Tamas K Lengyel
2016-04-12 16:24 ` Julien Grall
2016-04-12 17:05 ` Corneliu ZUZU
2016-04-12 17:24 ` Tamas K Lengyel
2016-04-13 8:55 ` Corneliu ZUZU
2016-04-13 10:17 ` Andrew Cooper
2016-04-13 10:53 ` Corneliu ZUZU
2016-04-13 12:02 ` Andrew Cooper
2016-04-13 13:25 ` Tamas K Lengyel
2016-04-13 15:06 ` Lars Kurth
2016-04-13 15:13 ` Tamas K Lengyel
2016-04-13 10:52 ` Julien Grall
2016-04-13 11:02 ` Corneliu ZUZU
2016-04-13 15:32 ` Tamas K Lengyel
2016-04-12 14:55 ` Konrad Rzeszutek Wilk
2016-04-12 15:22 ` Tamas K Lengyel
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='CABfawhmr1aG3pKZ0D9g6=KMzB1D5vtHg7jVivCm0J2TdWgc6Lg@mail.gmail.com' \
--to=tamas@tklengyel.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=keir@xen.org \
--cc=rcojocaru@bitdefender.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.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.