From: Jan Kiszka <jan.kiszka@web.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jailhouse-dev@googlegroups.com
Subject: Re: [PATCH 02/10] x86: jailhouse: Add infrastructure for running in non-root cell
Date: Sat, 18 Nov 2017 20:21:45 +0100 [thread overview]
Message-ID: <eaae5b29-3b4c-c772-83b2-a620bda1778a@web.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1711172248110.2186@nanos>
On 2017-11-17 22:54, Thomas Gleixner wrote:
> On Thu, 16 Nov 2017, Jan Kiszka wrote:
>
>> +config JAILHOUSE_GUEST
>> + bool "Jailhouse non-root cell support"
>> + depends on PARAVIRT && X86_64
>> + ---help---
>> + This option allows to run Linux as guest in a Jailhouse non-root
>> + cell. You can leave this option disabled if you only want to start
>> + Jailhouse and run Linux afterwards in the root cell.
>> +
>> + You likely also want to disable CONFIG_SUSPEND and CONFIG_SERIO to
>> + avoid access to I/O resources that are usually not assigned to the
>> + non-root cell.
>
> That should be prevented programatically.
Theoretically, serio access could also be assigned to a non-root cell.
But excluding SUSPEND may make sense unconditionally, will check again.
>
>> +#include <linux/kernel.h>
>> +#include <asm/cpu.h>
>> +#include <asm/hypervisor.h>
>> +#include <asm/setup.h>
>> +
>> +#define SETUP_JAILHOUSE 0x53484c4a /* "JLHS" */
>> +
>> +#define SETUP_REQUIRED_VERSION 1
>> +
>> +/*
>> + * The boot loader is passing platform information via this Jailhouse-specific
>> + * setup data structure.
>> + */
>> +struct jailhouse_setup_data {
>> + struct setup_data header;
>> + u16 version;
>> + u16 compatible_version;
>> + u16 pm_timer_address;
>> + u16 num_cpus;
>> + u64 pci_mmconfig_base;
>> + u8 standard_ioapic;
>> + u8 cpu_ids[255];
>
> Shouldn't this structure and SETUP_JAILHOUSE be defined in a header file
> which can be exported to boot loaders?
Something like arch/x86/include/uapi/asm/jailhouse_setup.h?
Jan
next prev parent reply other threads:[~2017-11-18 19:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 7:26 [PATCH 00/10] x86: Add support for running as secondary Jailhouse guest Jan Kiszka
2017-11-16 7:26 ` [PATCH 01/10] x86/apic: Install an empty physflat_init_apic_ldr Jan Kiszka
2017-11-17 21:43 ` Thomas Gleixner
2017-11-16 7:26 ` [PATCH 02/10] x86: jailhouse: Add infrastructure for running in non-root cell Jan Kiszka
2017-11-17 21:54 ` Thomas Gleixner
2017-11-18 19:21 ` Jan Kiszka [this message]
2017-11-20 11:22 ` Thomas Gleixner
2017-11-16 7:26 ` [PATCH 03/10] x86: jailhouse: Enable APIC and SMP support Jan Kiszka
2017-11-17 22:42 ` Thomas Gleixner
2017-11-20 14:39 ` Konrad Rzeszutek Wilk
2017-11-20 17:26 ` Thomas Gleixner
2017-11-16 7:26 ` [PATCH 04/10] x86: jailhouse: Enable PMTIMER Jan Kiszka
2017-11-17 22:44 ` Thomas Gleixner
2017-11-16 7:26 ` [PATCH 05/10] x86: jailhouse: Set up timekeeping Jan Kiszka
2017-11-17 22:49 ` Thomas Gleixner
2017-11-18 19:23 ` Jan Kiszka
2017-11-20 11:24 ` Thomas Gleixner
2017-11-20 12:21 ` Jan Kiszka
2017-11-23 18:36 ` Thomas Gleixner
2017-11-23 19:48 ` Jan Kiszka
2017-11-16 7:26 ` [PATCH 06/10] x86: jailhouse: Avoid access of unsupported platform resources Jan Kiszka
2017-11-17 22:57 ` Thomas Gleixner
2017-11-17 22:59 ` Thomas Gleixner
2017-11-16 7:26 ` [PATCH 07/10] x86: jailhouse: Silence ACPI warning Jan Kiszka
2017-11-16 7:26 ` [PATCH 08/10] x86: jailhouse: Halt instead of failing to restart Jan Kiszka
2017-11-16 7:26 ` [PATCH 09/10] x86: jailhouse: Wire up IOAPIC for legacy UART ports Jan Kiszka
2017-11-17 23:14 ` Thomas Gleixner
2017-11-16 7:26 ` [PATCH 10/10] x86: jailhouse: Initialize PCI support Jan Kiszka
2017-11-18 21:15 ` [PATCH 00/10] x86: Add support for running as secondary Jailhouse guest H. Peter Anvin
2017-11-20 7:00 ` 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=eaae5b29-3b4c-c772-83b2-a620bda1778a@web.de \
--to=jan.kiszka@web.de \
--cc=hpa@zytor.com \
--cc=jailhouse-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®