From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>, <daniel.sangorrin@toshiba.co.jp>,
<jan.kiszka@siemens.com>
Subject: Re: [cip-dev] [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config
Date: Fri, 7 Aug 2020 21:31:33 +0000 [thread overview]
Message-ID: <OSBPR01MB298341D4C5B082E32DB5587792490@OSBPR01MB2983.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <c0e08e23-2cc0-0ded-6266-2c4da2ccf4af@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]
Hi,
> -----Original Message-----
> From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Quirin Gylstorff
> Sent: Thursday, August 6, 2020 11:27 PM
> To: cip-dev@lists.cip-project.org; sangorrin daniel(サンゴリン ダニエル □ＳＷＣ◯ＡＣＴ)
> <daniel.sangorrin@toshiba.co.jp>; jan.kiszka@siemens.com
> Subject: Re: [cip-dev] [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config
>
>
>
> On 8/6/20 8:46 AM, Nobuhiro Iwamatsu wrote:
> > Hi,
> >
> > Thanks for your patch.
> >
> >> -----Original Message-----
> >> From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of Quirin Gylstorff
> >> Sent: Monday, August 3, 2020 7:12 PM
> >> To: cip-dev@lists.cip-project.org; sangorrin daniel(サンゴリン ダニエル □ＳＷＣ◯ＡＣＴ)
> >> <daniel.sangorrin@toshiba.co.jp>; jan.kiszka@siemens.com
> >> Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> >> Subject: [cip-dev] [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config
> >>
> >> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> >>
> >> If EFI_STUB is not active booting QEMU with OVMF efi will fail
> >> with the following error message `KVM internal error. Suberror: 3`.
> >>
> >> OVMF efi is used in isar-cip-core to demonstrate secure-boot with
> >> a unified kernel image.
> >>
> >> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> >> ---
> >> 4.19.y-cip/x86/cip_qemu_defconfig | 1 +
> >> 1 file changed, 1 insertion(+)
> >
> > Please update cip_qemu.sources too.
>
> When i try to generate the sources - all .c and asm files are no longer
> part of the cip-qemu.sources. Did I miss something? Or should I try
> again like the last time this happened?
Thanks for your check.
Sorry, I wanted to check if there was a fix in cip_qemu.sources.
I applied this patch.
> >
> Thanks,
> Quirin
Best regards,
Nobuhiro
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5106): https://lists.cip-project.org/g/cip-dev/message/5106
Mute This Topic: https://lists.cip-project.org/mt/75962579/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-08-07 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 10:12 [cip-dev] [cip-kernel-config PATCH] qemu_cip_defconfig: Add EFI_STUB to config Quirin Gylstorff
2020-08-06 6:46 ` Nobuhiro Iwamatsu
2020-08-06 14:26 ` Quirin Gylstorff
2020-08-07 21:31 ` Nobuhiro Iwamatsu [this message]
2020-08-20 8:50 ` Quirin Gylstorff
2020-08-20 23:08 ` Nobuhiro Iwamatsu
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=OSBPR01MB298341D4C5B082E32DB5587792490@OSBPR01MB2983.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.org \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=jan.kiszka@siemens.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.