public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Carlo Vitucci <vitucci.carlo@gmail.com>, jailhouse-dev@googlegroups.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Sabony, Mazda" <Mazda.Sabony@amd.com>
Subject: Re: Developer wanted: AMD64 port of Jailhouse hypervisor
Date: Wed, 23 Apr 2014 10:43:40 +0200	[thread overview]
Message-ID: <53577D3C.5060103@siemens.com> (raw)
In-Reply-To: <b95ba76d-c3a9-458e-b9a9-10ca28886d55@googlegroups.com>

On 2014-04-23 08:21, Carlo Vitucci wrote:
> Il giorno lunedì 14 aprile 2014 20:27:16 UTC+2, J. Kiszka ha scritto:
>> Hi all,
>>
>>
>>
>> so far the Linux-based Jailhouse hypervisor [1] is only available for
>>
>> Intel x86 CPUs. I'm now very happy to announce that AMD is offering to
>>
>> sponsor the initial port of Jailhouse to the AMD64 architecture. Our
>>
>> resources here are unfortunately bound to different tasks, but if anyone
>>
>> out there with the required skills is interested in working on this
>>
>> project, just reply to this email or contact me and Mazda directly.
>>
>>
>>
>> The work to be done is manageable: we basically need corresponding
>>
>> implementations of vmx.c and vtd.c in the current Jailhouse code base -
>>
>> provided our existing abstractions were done right. Someone familiar
>>
>> with virtualization on x86 in general and, ideally, even on AMD
>>
>> processors should be able to complete this task within a couple of weeks.
>>
>>
>>
>> For more details on the Jailhouse architecture and implementations, see
>>
>> our slowly growing Documentation folder in the source tree or simply ask
>>
>> on the mailing list.
>>
>>
>>
>> Jan
>>
>>
>>
>> [1] https://github.com/siemens/jailhouse
>>
>>
>>
>> -- 
>>
>> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
>>
>> Corporate Competence Center Embedded Linux
> 
> Hello jailhouse,
>  just a thought, if I could. AMD64 is not officially delivered and one
>  of the most important new features, that is the direct interrupt delivery,
>  is without a final specification. in other words, ARMv8 is the only suitable
>  architecture for Jailhouse porting, but there is still a bit fog around.

I'm not sure if I got your point yet: AMD64 stands for the
well-established x86-64 architecture with AMD-specific parts like the
virtualization extensions. All these transistors and specs are broadly
available for years.

Regarding direct interrupt delivery: on Intel, we do not depend on
specific hardware support to provide this feature, and I bet we can port
that approach to AMD as well.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2014-04-23  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 18:27 Developer wanted: AMD64 port of Jailhouse hypervisor Jan Kiszka
2014-04-23  6:21 ` Carlo Vitucci
2014-04-23  8:43   ` Jan Kiszka [this message]
2014-04-23  8:49     ` Carlo Vitucci
2014-04-23  8:54       ` Jan Kiszka

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=53577D3C.5060103@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Mazda.Sabony@amd.com \
    --cc=jailhouse-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vitucci.carlo@gmail.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