Date
1 - 14 of 14
UOS kernel
|
Ross Burton
Hi,
Obviously the SOS needs the acrn patches (which I'm obtaining via linux-intel-lts) but are there any UOS-specific patches in that kernel tree too? Does any modern kernel work as well, or are there patches and/or kconfig options that improve the guest performance? Thanks, Ross
|
|
|
|
Ross Burton
Hit send way too early. Obviously virtio and friends need to be
toggle quoted messageShow quoted text
enabled. Is any *KVM guest enabled* kernel suitable, or are there further guest improvements in the acrn-kernel tree? Ross
On Wed, 13 Feb 2019 at 21:50, Burton, Ross <ross.burton@intel.com> wrote:
|
|
|
|
I had started looking into this a bit since I knew the engineering was mostly out on holiday last week, the quick summary is that there are at least a number of virtio FE drivers that are not upstream (yet): RPMB, HECI, Audio, IPU, TSN, HyperDMA buffer, HDCP and COREU (see [1]). You may not need all of them but I suspect you'll want at least a few. I think this is pretty much it for the User OS kernel but I will let the engineering confirm that.
toggle quoted messageShow quoted text
Geoffroy [1] https://projectacrn.github.io/latest/developer-guides/hld/hld-virtio-devices.html#virtio-device-table
-----Original Message-----
|
|
|
|
Tzeng, Tonny <tonny.tzeng@...>
Hi Ross,
toggle quoted messageShow quoted text
You can reference tons of patches in the Clear Linux package repo [1], if you want to build the SOS from the upstream kernel, instead of using the acrn-kernel tree. Alternative is to use the Clear Linux developer tooling framework [2] to rebuild the SOS. FYI. [1] https://github.com/clearlinux-pkgs/linux-iot-lts2018 [2] https://github.com/clearlinux/common Regards, Tonny
-----Original Message-----
From: acrn-users@lists.projectacrn.org [mailto:acrn-users@lists.projectacrn.org] On Behalf Of Ross Burton Sent: Thursday, February 14, 2019 5:52 AM To: acrn-users@lists.projectacrn.org Subject: Re: [acrn-users] UOS kernel Hit send way too early. Obviously virtio and friends need to be enabled. Is any *KVM guest enabled* kernel suitable, or are there further guest improvements in the acrn-kernel tree? Ross On Wed, 13 Feb 2019 at 21:50, Burton, Ross <ross.burton@intel.com> wrote:
|
|
|
|
Ross Burton
On Wed, 13 Feb 2019 at 23:52, Tzeng, Tonny <tonny.tzeng@intel.com> wrote:
You can reference tons of patches in the Clear Linux package repo [1], if you want to build the SOS from the upstream kernel, instead of using the acrn-kernel tree. Alternative is to use the Clear Linux developer tooling framework [2] to rebuild the SOS. FYI.linux-iot-lts2018 is Intel Production Kernel with two Clear-specific patches on top. We already build the Production Kernel for our IA BSP, so I'm just using a custom defconfig. Ross
|
|
|
|
Ross Burton
That's good to know. Our 'standard' kernel is linux-intel-lts so it
will have all the acrn-kernel patches in already, we just need to make sure they're enabled. Ross On Wed, 13 Feb 2019 at 23:41, Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com> wrote:
|
|
|
|
toggle quoted messageShow quoted text
-----Original Message-----So that may not turn out to be too hard to do then, good! :) Geoffroy
|
|
|
|
Tim Orling
On Feb 13, 2019, at 4:05 PM, Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com> wrote:We're successfully running ACRN v0.6 SOS and UOS on either a 4.19.19 or 4.19.23 PKT kernel on Skull Canyon (NUC6i7KYK).-----Original Message-----So that may not turn out to be too hard to do then, good! :) However, once we start the UOS, we see a repeating infinite loop of: [232000.725079] gvt: vgpu 1: Unsupport pipe 0, scaler 0 scaling [232000.725105] gvt: vgpu 1: Unsupport pipe 0, scaler 0 scaling [232000.725124] gvt: vgpu 1: Unsupport pipe 0, scaler 0 scaling [232000.725144] gvt: vgpu 1: Unsupport pipe 0, scaler 1 scaling [232000.725188] gvt: vgpu 1: Unsupport pipe 0, scaler 1 scaling [232000.725208] gvt: vgpu 1: Unsupport pipe 0, scaler 1 scaling This error is being generated by skl_ps_mmio_write(...) in drivers/gpu/drm/i915/gvt/handlers.c: https://github.com/intel/linux-intel-lts/blob/4.19/base/drivers/gpu/drm/i915/gvt/handlers.c#L3017 which is in turn being called by pvmmio_update_plane_register(...) also in drivers/gpu/drm/i915/gvt/handlers.c: https://github.com/intel/linux-intel-lts/blob/4.19/base/drivers/gpu/drm/i915/gvt/handlers.c#L825 I haven't wrapped my head around it yet, but when we instrumented via printk we see "; scaler_owner 0 != vgpu->id 1" It seems like it is related to: https://projectacrn.github.io/0.6/developer-guides/GVT-g-kernel-options.html?highlight=scaler#i915-domain-scaler-owner Is i915.domain_scaler_owner able to be set on kernel command line? Any suggestions what value should be used?
|
|
|
|
He, Min
Hi Tim,
toggle quoted messageShow quoted text
-----Original Message-----Actually you can ignore this kind of messages. Please just replace gvt_vgpu_err with a gvt_dbg_dpy(). Yes, i915.domain_scaler_owner can be set through SOS kernel command line. It depends on your configuration. If you assigned all the planes on a pipe to the UOS, you can assign all the scalers on that pipe to UOS. mostly
|
|
|
|
Ross Burton
On Tue, 5 Mar 2019 at 01:43, He, Min <min.he@intel.com> wrote:
So if we have:Is i915.domain_scaler_owner able to be set on kernel command line? AnyYes, i915.domain_scaler_owner can be set through SOS kernel command line. It depends on i915.domain_plane_owners=0x011111110000 Then a corresponding i915.domain_scalar_owner would be: i915.domain_scalar_owner=0x011100 Right? I guess the important thing to do is dig out the pipe/plane layout and verify that our target has the same geometry as the Broxton in the documentation. Also the singular/plural difference in domain_plane_owners vs domain_scalar_owner is driving me insane, can this be fixed? Ross
|
|
|
|
He, Min
toggle quoted messageShow quoted text
-----Original Message-----Yes, it's the correct configuration. Also the singular/plural difference in domain_plane_owners vsSorry for this kind of confusion. Yes, we should fix it, we will submit patch in next release window. Thanks for pointing this out.
|
|
|
|
Ross Burton
On Wed, 6 Mar 2019 at 01:11, He, Min <min.he@intel.com> wrote:
I just noticed that I'm getting warnings when we set this:On Tue, 5 Mar 2019 at 01:43, He, Min <min.he@intel.com> wrote:line. It depends onIs i915.domain_scaler_owner able to be set on kernel command line? AnyYes, i915.domain_scaler_owner can be set through SOS kernel command [ 7.790940] i915: unknown parameter 'domain_scalar_owner' ignored Indeed: ross@flashheart ~/Programming/acrn-kernel (master) $ git grep domain_scalar | wc -l 0 Is this option not in acrn-kernel yet, or has it been removed? Ross
|
|
|
|
toggle quoted messageShow quoted text
-----Original Message-----This is a typo, it should be domain_scaler_owner - see: - https://projectacrn.github.io/latest/developer-guides/GVT-g-kernel-options.html#i915-domain-scaler-owner - https://github.com/projectacrn/acrn-kernel/blob/master/drivers/gpu/drm/i915/i915_params.c#L184-L204 Geoffroy
|
|
|
|
Ross Burton
On Tue, 12 Mar 2019 at 16:25, Geoffroy Van Cutsem
<geoffroy.vancutsem@intel.com> wrote: <facepalm>Is this option not in acrn-kernel yet, or has it been removed?This is a typo, it should be domain_scaler_owner - see: Thanks. Ross
|
|
|