From: Mark Rutland <mark.rutland@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: marc.zyngier@arm.com, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, dave.martin@arm.com
Subject: Re: [PATCH 1/2] arm/kvm: survive unknown traps from guests
Date: Mon, 6 Mar 2017 17:33:30 +0000 [thread overview]
Message-ID: <20170306173330.GH18519@leverpostej> (raw)
In-Reply-To: <20170306150803.GB1502@lvm>
On Mon, Mar 06, 2017 at 07:08:03AM -0800, Christoffer Dall wrote:
> On Mon, Feb 20, 2017 at 12:30:11PM +0000, Mark Rutland wrote:
> > static exit_handle_fn arm_exit_handlers[] = {
> > + [0 ... HSR_EC_MAX] = kvm_handle_unknown_ec,
>
> Cool stuff, didn't know you could do this in C.
Strictly speaking, it's a GCC-ism, though we use it all over the place:
[mark@leverpostej:~/src/linux]% git grep '\[.*\.\.\..*\]\s=' | wc -l
394
It may also make checkpatch a bit grumpy, though I think that's being
worked on.
> Reviewed-by: Christoffer Dall <cdall@linaro.org>
Cheers!
I assume you or Marc will pick this up?
Thanks,
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm/kvm: survive unknown traps from guests
Date: Mon, 6 Mar 2017 17:33:30 +0000 [thread overview]
Message-ID: <20170306173330.GH18519@leverpostej> (raw)
In-Reply-To: <20170306150803.GB1502@lvm>
On Mon, Mar 06, 2017 at 07:08:03AM -0800, Christoffer Dall wrote:
> On Mon, Feb 20, 2017 at 12:30:11PM +0000, Mark Rutland wrote:
> > static exit_handle_fn arm_exit_handlers[] = {
> > + [0 ... HSR_EC_MAX] = kvm_handle_unknown_ec,
>
> Cool stuff, didn't know you could do this in C.
Strictly speaking, it's a GCC-ism, though we use it all over the place:
[mark at leverpostej:~/src/linux]% git grep '\[.*\.\.\..*\]\s=' | wc -l
394
It may also make checkpatch a bit grumpy, though I think that's being
worked on.
> Reviewed-by: Christoffer Dall <cdall@linaro.org>
Cheers!
I assume you or Marc will pick this up?
Thanks,
Mark.
next prev parent reply other threads:[~2017-03-06 17:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 12:30 [PATCH 0/2] arm{,64}/kvm: survive unknown traps from guests Mark Rutland
2017-02-20 12:30 ` Mark Rutland
2017-02-20 12:30 ` [PATCH 1/2] arm/kvm: " Mark Rutland
2017-02-20 12:30 ` Mark Rutland
2017-03-06 15:08 ` Christoffer Dall
2017-03-06 15:08 ` Christoffer Dall
2017-03-06 17:33 ` Mark Rutland [this message]
2017-03-06 17:33 ` Mark Rutland
2017-03-07 7:54 ` Marc Zyngier
2017-03-07 7:54 ` Marc Zyngier
2017-02-20 12:30 ` [PATCH 2/2] arm64/kvm: " Mark Rutland
2017-02-20 12:30 ` Mark Rutland
2017-02-20 13:48 ` Suzuki K Poulose
2017-02-20 13:48 ` Suzuki K Poulose
2017-02-20 14:01 ` Mark Rutland
2017-02-20 14:01 ` Mark Rutland
2017-03-06 15:08 ` Christoffer Dall
2017-03-06 15:08 ` 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=20170306173330.GH18519@leverpostej \
--to=mark.rutland@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=dave.martin@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.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 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.