linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2012-discuss] ARM mini-summit
Date: Wed, 11 Jul 2012 23:16:09 +0200	[thread overview]
Message-ID: <061ef00be9b475973e5df22fcd096308@localhost> (raw)
In-Reply-To: <201207112006.28632.arnd@arndb.de>

On Wed, 11 Jul 2012 20:06:28 +0000, Arnd Bergmann <arnd@arndb.de> wrote:
> On Wednesday 11 July 2012, Konrad Rzeszutek Wilk wrote:
>> >> > contacts, with Grant and Olof joining in as time permits.
>> >>
>> >> Acked-by: Grant Likely <grant.likely@secretlab.ca>
>> >
>> > I would be interested in attending it as well. I believe Stefano has
a
>> > strong
>> > interest as well (since he and Ian Campbell are leading the Xen ARM
>> > work).
>> 
>> And Stefano is out on vacation right now so I will serve as his phantom
>> voice
>> and say: "Yes, I am interested as well."
> 
> Ok. So are you mostly interested in discussion ARM virtualization or
other
> topics
> as well? Last time we had organized this explicitly as the "ARM subarch
> maintainer
> summit" and we might again limit the participants to the subarch
> maintainers and
> a few more people if we're running out of space, but then again if a lot
> of them
> are interested in discussion virtualization, we should probably have you
> both and 
> the ARM KVM people included as well.
> 
> We haven't even started discussing an agenda, but I'll note down your
> names as
> candidates and Xen and/or KVM as proposed topics. I'll follow up with a
> more
> formal call for topics once I have a positive confirmation from James
and
> the
> linux-foundation that we can go ahead with the ARM mini-summit.

Putting on my KVM/ARM hacker hat this time: I'd be very glad to contribute
to the discussion. There is a number of ARM-specific topics that would be
interesting to discuss regarding KVM/ARM (mainlining the damn thing, common
hypercalls?, HYP mode booting), and probably a couple of other things.

Cheers,

        M.
-- 
Fast, cheap, reliable. Pick two.

  parent reply	other threads:[~2012-07-11 21:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1341994155.3522.16.camel@dabdike.int.hansenpartnership.com>
2012-07-11 11:28 ` ARM mini-summit Arnd Bergmann
2012-07-11 11:57   ` [Ksummit-2012-discuss] " Catalin Marinas
2012-07-11 12:35     ` Marc Zyngier
2012-07-12 22:08       ` Kukjin Kim
2012-07-13  7:18         ` Tony Lindgren
2012-07-27 13:57           ` Igor Grinberg
2012-07-11 12:15   ` Grant Likely
2012-07-11 14:05     ` [Ksummit-2012-discuss] " Konrad Rzeszutek Wilk
2012-07-11 19:27       ` Konrad Rzeszutek Wilk
2012-07-11 20:06         ` Arnd Bergmann
2012-07-11 20:11           ` Konrad Rzeszutek Wilk
2012-07-11 21:16           ` Marc Zyngier [this message]
2012-07-11 21:58             ` Rob Herring
2012-07-12 13:58             ` Stefano Stabellini
2012-07-12 13:31         ` Stefano Stabellini
2012-07-11 21:02   ` David Brown
2012-07-13  2:33   ` Olof Johansson

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=061ef00be9b475973e5df22fcd096308@localhost \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).