On 19.08.2023 02:28, Vikram Garhwal wrote:
> Rename iommu_dt_device_is_assigned() to iommu_dt_device_is_assigned_locked().
> Remove static type so this can also be used by SMMU drivers to check if the
> device is being used before removing.
>
> Moving spin_lock to caller was done to prevent the co
On 18.08.2023 21:52, Vikram Garhwal wrote:
> On Thu, Aug 17, 2023 at 09:05:44AM +0200, Jan Beulich wrote:
>> On 17.08.2023 02:39, Vikram Garhwal wrote:
>>> --- /dev/null
>>> +++ b/xen/include/xen/iommu-private.h
>>
>> I don't think private headers should live in include/xen/. Judging from only
>> t
Hi Julien,
On Fri, Aug 18, 2023 at 10:32 AM Julien Grall wrote:
>
> Hi Jens,
>
> On 31/07/2023 13:15, Jens Wiklander wrote:
> > Jens Wiklander (14):
> >xen/arm: ffa: add direct request support
> >xen/arm: ffa: map SPMC rx/tx buffers
> >xen/arm: ffa: send guest events to Secure Partiti
We are doing foreign memory mapping for static shared memory, and
there is a great possibility that it could be super mapped.
But today, p2m_put_l3_page could not handle superpages.
This commits implements a new function p2m_put_superpage to handle superpages,
specifically for helping put extra re
This commit amends docs(docs/misc/arm/device-tree/booting.txt) to include the
new scenario where host address is not provided in "xen,shared-mem" property,
and we also add a new example to explain in detail.
We also fix some buggy info in the docs, like SHMID is "my-shared-mem-1",
not "0x1".
Sign
Static shared memory acts as reserved memory in guest, so it shall be
excluded from extended regions.
Extended regions are taken care of under three different scenarios:
normal DomU, direct-map domain with iommu on, and direct-map domain
with iommu off.
For normal DomU, we create a new function "
In order to support static shared memory when host address not provided,
we shall do the following modification:
- we shall let Xen allocate memory from heap for static shared memory
at first domain, no matter it is owner or borrower.
- In acquire_shared_memory_bank, as static shared memory has alr
We use paddr_assigned to indicate whether host address is provided, by
checking the length of "xen,shared-mem" property.
The shm matching criteria shall also be adapt to cover the new scenario, by
adding when host address is not provided, if SHMID matches, the region size
must exactly match too.
We split the code of allocate_bank_memory into two parts,
allocate_domheap_memory and guest_physmap_memory.
One is about allocating guest RAM from heap, which could be re-used later for
allocating static shared memory from heap when host address is not provided.
The other is building up guest P2M
This commit introduces a set of separate data structures to deal with
static shared memory at different stages.
In boot-time host device tree parsing, we introduce a new structure
"struct shm_node" and a new field "shm_info" in bootinfo to describe and
store parsed shm info.
only SHMID and "nr_bor
Function parameters {addr_cells,size_cells} are stale parameters in
assign_shared_memory, so we shall remove them.
Signed-off-by: Penny Zheng
---
v1 -> v2:
- new commit
---
v2 -> v3:
rebase and no change
---
xen/arch/arm/domain_build.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/xen/arc
There are some unsolving issues on current 4.17 static shared memory
feature[1], including:
- In order to avoid keeping growing 'membank', having the shared memory
info in separate structures is preferred.
- Missing implementation on having the host address optional in
"xen,shared-mem" property
- R
flight 182405 linux-linus real [real]
flight 182407 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/182405/
http://logs.test-lab.xenproject.org/osstest/logs/182407/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-
On 8/17/23 08:57, Jan Beulich wrote:
> On 16.08.2023 20:50, Stewart Hildebrand wrote:
>> If there are no capabilities to be exposed to the guest, a future status
>> register handler likely would want to mask the PCI_STATUS_CAP_LIST bit. See
>> [1]
>> for a suggestion of how this might be tracked i
flight 182403 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/182403/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-examine-bios 6 xen-install fail in 182400 pass in 182403
test-amd64-amd64-xl-qemuu-win7-a
flight 182402 linux-linus real [real]
flight 182404 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/182402/
http://logs.test-lab.xenproject.org/osstest/logs/182404/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run
flight 182400 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/182400/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm broken in 182397
test-amd64-amd64-xl-qemuu-win7
flight 182399 linux-linus real [real]
flight 182401 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/182399/
http://logs.test-lab.xenproject.org/osstest/logs/182401/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-
18 matches
Mail list logo