On Sun, May 30, 2021 at 11:06:27AM -0400, Tianyu Lan wrote:
> + if (hv_isolation_type_snp()) {
> + pfns = kcalloc(buf_size / HV_HYP_PAGE_SIZE, sizeof(unsigned
> long),
> +GFP_KERNEL);
> + for (i = 0; i < buf_size / HV_HYP_PAGE_SIZE; i++)
> +
On Sun, May 30, 2021 at 11:06:28AM -0400, Tianyu Lan wrote:
> + for (i = 0; i < request->hvpg_count; i++)
> + dma_unmap_page(&device->device,
> +
> request->dma_range[i].dma,
> +
Honestly, we really need to do away with the concept of hypervisor-
specific swiotlb allocations and just add a hypervisor hook to remap the
"main" buffer. That should remove a lot of code and confusion not just
for Xen but also any future addition like hyperv.
On Sun, May 30, 2021 at 11:06:25AM -0400, Tianyu Lan wrote:
> From: Tianyu Lan
>
> For Hyper-V isolation VM with AMD SEV SNP, the bounce buffer(shared memory)
> needs to be accessed via extra address space(e.g address above bit39).
> Hyper-V code may remap extra address space outside of swiotlb.
On Sun, May 30, 2021 at 11:06:18AM -0400, Tianyu Lan wrote:
> + if (ms_hyperv.ghcb_base) {
> + rdmsrl(MSR_AMD64_SEV_ES_GHCB, ghcb_gpa);
> +
> + ghcb_va = ioremap_cache(ghcb_gpa, HV_HYP_PAGE_SIZE);
> + if (!ghcb_va)
> + return -ENOMEM;
Can
On 05/06/2021 19.50, Ahmed Abouzied wrote:
Identifiers with leading underscores followed by capital letters or
underscores are reserved for C standards.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/369
Signed-off-by: Ahmed Abouzied
---
include/hw/xen/interface/grant_table.h | 4 +
On 03.06.2021 15:08, Tim Deegan wrote:
> Better reflect reality: Andrew and Jan are active maintainers
> and I review patches. Keep myself as a reviewer so I can help
> with historical context &c.
>
> Signed-off-by: Tim Deegan
Largely for formal reasons
Acked-by: Jan Beulich
> --- MAINTAINERS
On 07.06.2021 04:43, Penny Zheng wrote:
> --- a/xen/arch/arm/Kconfig
> +++ b/xen/arch/arm/Kconfig
> @@ -278,6 +278,9 @@ config ARM64_ERRATUM_1286807
>
> If unsure, say Y.
>
> +config STATIC_ALLOCATION
> +def_bool y
> +
> endmenu
>
> config ARM64_HARDEN_BRANCH_PREDICTOR
Nit: Whi
flight 162463 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162463/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
test-amd64-i386-xl-
Hi Christoph,
On 6/1/21 11:53 PM, Christoph Hellwig wrote:
> Use the blk_mq_alloc_disk API to simplify the gendisk and request_queue
> allocation.
>
> drivers/block/ps3disk.c | 36 ++--
> 1 file changed, 14 insertions(+), 22 deletions(-)
I tested your alloc_disk-
On Sat, Jun 5, 2021 at 1:48 AM Will Deacon wrote:
>
> Hi Claire,
>
> On Thu, May 27, 2021 at 08:58:30PM +0800, Claire Chang wrote:
> > This series implements mitigations for lack of DMA access control on
> > systems without an IOMMU, which could result in the DMA accessing the
> > system memory at
flight 162470 xen-unstable-smoke real [real]
flight 162478 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/162470/
http://logs.test-lab.xenproject.org/osstest/logs/162478/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which co
This commit introduces allocate_static_memory to allocate static memory as
guest RAM for Domain on Static Allocation.
It uses alloc_domstatic_pages to allocate pre-configured static memory banks
for this domain, and uses guest_physmap_add_page to set up P2M table.
These pre-defiend static memory r
In the future, user may want to allocate static memory at runtime,
and it is quite important to get the code protected from concurrent
access.
Re-use heap_lock to protect concurrent access in alloc_staticmem_pages.
Signed-off-by: Penny Zheng
---
changes v2:
- new commit
---
xen/common/page_allo
This commit checks `xen,static-mem` device tree property in /domUx node,
to determine whether domain is on Static Allocation, when constructing
domain during boot-up.
Right now, the implementation of allocate_static_memory is missing, and
will be introduced later. It just BUG() out at the moment.
alloc_staticmem_pages aims to allocate nr_mfns contiguous pages of
static memory. And it is the equivalent of alloc_heap_pages for static
memory. Here only covers allocating at specified starting address.
For each page, it shall check if the page is reserved(PGC_reserved)
and free. It shall also d
Introduce new interface assign_pages_nr to deal with when page number is
not in a power-of-two, which will save the trouble each time user needs
to split the size in a power of 2 to use assign_pages.
Signed-off-by: Penny Zheng
---
changes v2:
- introduce new interface assign_pages_nr
---
xen/com
This patch introduces static memory initialization, during system RAM boot up.
New func init_staticmem_pages is responsible for static memory initialization.
Helper free_staticmem_pages is the equivalent of free_heap_pages, to free
nr_mfns pages of static memory.
This commit defines a new helper
For now, since the feature of Domain on Static Allocation is only supported
on ARM Architecture, this commit introduces new CONFIG_STATIC_ALLOCATION to
avoid bringing dead codes in other archs.
Signed-off-by: Penny Zheng
---
changes v2:
- new commit
---
xen/arch/arm/Kconfig | 3 +++
1 file chang
In order to differentiate pages of static memory, from those allocated from
heap, this patch introduces a new page flag PGC_reserved to tell.
Signed-off-by: Penny Zheng
---
changes v2:
- remove unused reserved field in struct page_info
- remove unused helper page_get_reserved_owner and page_set_r
Static Allocation refers to system or sub-system(domains) for which memory
areas are pre-defined by configuration using physical address ranges.
Those pre-defined memory, -- Static Memory, as parts of RAM reserved in the
beginning, shall never go to heap allocator or boot allocator for any use.
Do
Static Allocation refers to system or sub-system(domains) for which memory
areas are pre-defined by configuration using physical address ranges.
Those pre-defined memory, -- Static Memory, as parts of RAM reserved in the
beginning, shall never go to heap allocator or boot allocator for any use.
Th
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemuu-ovmf-amd64
testid debian-hvm-install
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xen
flight 162454 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162454/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-freebsd11-amd64 16 guest-saverestore fail REGR. vs.
152631
test-amd64-am
flight 162461 xen-unstable-smoke real [real]
flight 162467 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/162461/
http://logs.test-lab.xenproject.org/osstest/logs/162467/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which co
flight 162433 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162433/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemuu-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
test-amd64-i386-qem
flight 162453 xen-unstable-smoke real [real]
flight 162459 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/162453/
http://logs.test-lab.xenproject.org/osstest/logs/162459/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which co
flight 162446 xen-unstable-smoke real [real]
flight 162450 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/162446/
http://logs.test-lab.xenproject.org/osstest/logs/162450/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which co
flight 162429 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162429/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-freebsd11-amd64 16 guest-saverestore fail REGR. vs.
152631
test-amd64-am
flight 162436 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162436/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail like 162371
test-amd64-amd64-xl-qemuu-ovmf-amd64 12 debi
flight 162422 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162422/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl-rtds 18 guest-start/debian.repeatfail like 162330
test-amd64-amd64-xl-qemut-win7-amd64
flight 162441 xen-unstable-smoke real [real]
flight 162444 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/162441/
http://logs.test-lab.xenproject.org/osstest/logs/162444/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which co
flight 162432 xen-unstable-smoke real [real]
flight 162437 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/162432/
http://logs.test-lab.xenproject.org/osstest/logs/162437/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which co
flight 162427 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162427/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
flight 162420 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162420/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemuu-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
test-amd64-i386-qem
35 matches
Mail list logo
