On 07.05.19 16:13, Hakkı Kurumahmut wrote:
7 Mayıs 2019 Salı 08:52:46 UTC+3 tarihinde Jan Kiszka yazdı:
On 06.05.19 20:38, Hakkı Kurumahmut wrote:
6 Mayıs 2019 Pazartesi 18:19:07 UTC+3 tarihinde [email protected] yazdı:
For sure ! You can find the requested file attached.
best regards,
Le lundi 6 mai 2019 16:11:05 UTC+2, Jan Kiszka a écrit :
On 06.05.19 15:47, [email protected] wrote:
Hello,
I'm trying to run jailhouse on a HP ProLiant ML350 Gen10.
ACPI DMAR is available, but my hardware-check fails with this
error :
"Unsupported DMAR Device Scope Structure"
I also tried on a HP ProLiant DL360p Gen8 but I ended up with the same error...
Any idea of this trouble ?
Can you share an archive generated by "jailhouse config collect"? Then we can
analyze locally.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
DMAR region parser is detected Device Scope size more than 8 byte.
VT-d Spec at 8.3.1
If the ‘Path’ field length is more than 2 bytes (N > 1), the Device Scope
Entry identifies a device behind one or more system software visible PCI-
PCI bridges. Bus rebalancing actions by system software modifying bus
assignments of the device’s parent bridge impacts the bus number portion
of device’s requester-id.
This devices
1C.7.0.0
1C.7.0.2
Current Script does not support this type device... Scripts must be read Dev
Scope length and than it is read the DMAR file to collect correct data.
Jan can provide technical information on this issue. I have no idea why it's
not supported.
I think I was "just" too lazy to implement the needed logic behind that.
The tricky thing here is surely the identification of the final bus number the
BIOS or Linux as chosen for the device described that way. It will be needed in
order to identify the device entry in our configuration. Likely, we have to walk
the topology, first identify the bridge and then query that one for its bus
number in order to describe the device.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
Hi Jan,
I think that I have found a method to scan bridge device.
1. At DMAR file get starting bus number device and function number.
2. Open the target pci device config file.
3. Check Type-1 configuration space
4. Check primary bus number at 18h with DMAR starting bus number.
5. Get secondary bus number at 19h.
6. Return Secondary bus number, secondary device number and secondary function
number.
Dou you agree?
Yes, that sounds good!
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jailhouse-dev/5c94104f-c27d-9074-1990-61fa9e9d05c1%40siemens.com.
For more options, visit https://groups.google.com/d/optout.
