On Tue, Jul 18, 2017 at 11:46 PM, Julien Grall wrote:
> Hi,
>
>
> On 18/07/17 16:29, Wei Liu wrote:
>>
>> On Tue, Jul 18, 2017 at 05:11:30PM +0530, vijay.kil...@gmail.com wrote:
>> [...]
>>>
>>> diff --git a/xen/common/numa.c b/xen/common/numa.c
>>> new file mode 100644
>>> index 000..0381f1b
flight 111981 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111981/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 16 guest-localmigrate/x10 fail REGR. vs.
111957
Tests which
On Tue, Jul 18, 2017 at 8:59 PM, Wei Liu wrote:
> On Tue, Jul 18, 2017 at 05:11:27PM +0530, vijay.kil...@gmail.com wrote:
>> From: Vijaya Kumar K
>>
>> Add accessors for nodes[] and other static variables and
>> use those accessors. These variables are later accessed
>> outside the file when the
On Tue, Jul 18, 2017 at 9:06 PM, Wei Liu wrote:
> On Tue, Jul 18, 2017 at 05:11:40PM +0530, vijay.kil...@gmail.com wrote:
>> From: Vijaya Kumar K
>>
>> Move SRAT handling code which is common across
>> architectures is moved to new file xen/drivers/acpi/srat.c
>> from xen/arch/x86/srat.c file. Ne
On Tue, Jul 18, 2017 at 9:48 PM, Julien Grall wrote:
> Hi,
>
> On 18/07/17 12:41, vijay.kil...@gmail.com wrote:
>>
>> This patch is tested on Thunderx platform.
>> No changes are made to x86 implementation only code is sanitized
>> and refactored. Hence only compilation tested for x86.
>>
>> This
>
> Dear Andrii Anisov,
Thank you for the reply.
We are using R-Car H3 salvator X.
> It really depends on the setup you need.
Our plan is to run Linux as Dom0 and Android as DomU. The Linux portion
will be having 1 HDMI display and the Android porion will be having 1 HDMI.
Can we share the DU a
Hi Roger,
On 06/23/2017 08:57 PM, Roger Pau Monné wrote:
> On Thu, Jun 22, 2017 at 09:36:52AM +0800, Junxiao Bi wrote:
>> When ring buf full, hw queue will be stopped. While blkif interrupt consume
>> request and make free space in ring buf, hw queue will be started again.
>> But since start queue
On Tue, Jul 18, 2017 at 9:35 PM, H. Peter Anvin wrote:
> On 07/18/17 15:33, Thomas Garnier wrote:
>> With PIE support and KASLR extended range, the modules may be further
>> away from the kernel than before breaking mcmodel=kernel expectations.
>>
>> Add an option to build modules with mcmodel=lar
Add a new struct libxl_static_shm in the libxl IDL for the proposed new xl
config entry 'static_shm' (see [1]), which allow the user to set up shared
memory areas among several VMs for communication.
Add related parsing code to the libxl/libxlu_* family and xl/xl_parse.c
[1]: [RFC v3]Proposal to
On Tue, Jul 18, 2017 at 6:33 PM, Thomas Garnier wrote:
> Perpcu uses a clever design where the .percu ELF section has a virtual
> address of zero and the relocation code avoid relocating specific
> symbols. It makes the code simple and easily adaptable with or without
> SMP support.
>
> This desig
On Tue, Jul 18, 2017 at 6:33 PM, Thomas Garnier wrote:
> Change the assembly code to use only relative references of symbols for the
> kernel to be PIE compatible. The new __ASM_GET_PTR_PRE macro is used to
> get the address of a symbol on both 32 and 64-bit with PIE support.
>
> Position Independ
On 07/18/17 15:33, Thomas Garnier wrote:
> With PIE support and KASLR extended range, the modules may be further
> away from the kernel than before breaking mcmodel=kernel expectations.
>
> Add an option to build modules with mcmodel=large. The modules generated
> code will make no assumptions on
Forget to restrict the possible values of begin/end.
2017-07-19 2:30 GMT+08:00 Zhongze Liu :
>
> 1. Motivation and Description
>
> Virtual machines use grant table hypercalls to setup a share
On Tue, Jul 18, 2017 at 03:29:14PM -0700, Stefano Stabellini wrote:
> On Mon, 3 Jul 2017, Stefano Stabellini wrote:
> > On Mon, 3 Jul 2017, Owen Smith wrote:
> > > Backends set "feature-raw-pointer" if its capable of reporting
> > > absolute positions without scaling the coordinates to screen
> > >
flight 111993 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111993/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt 13 mig
flight 111972 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111972/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 7 xen-boot fail REGR.
vs. 110515
test-amd64
On 7/18/2017 10:21 PM, Roger Pau Monné wrote:
On Tue, Jul 18, 2017 at 08:36:15PM +1200, Huang, Kai wrote:
On 7/17/2017 10:54 PM, Roger Pau Monné wrote:
On Sun, Jul 09, 2017 at 08:16:05PM +1200, Kai Huang wrote:
On physical machine EPC is exposed in ACPI table via "INT0E0C". Although EPC
ca
On 7/18/2017 10:12 PM, Andrew Cooper wrote:
On 09/07/17 09:04, Kai Huang wrote:
Expose SGX in CPU featureset for HVM domain. SGX will not be supported for
PV domain, as ENCLS (which SGX driver in guest essentially runs) must run
in ring 0, while PV kernel runs in ring 3. Theoretically we can s
Change the relocation tool to correctly handle DYN/PIE kernel where
the relocation table does not reference symbols and percpu support is
not needed. Also add support for R_X86_64_RELATIVE relocations that can
be handled like a 64-bit relocation due to the usage of -Bsymbolic.
Position Independent
The x86 relocation tool generates a list of 32-bit signed integers. There
was no need to use 64-bit integers because all addresses where above the 2G
top of the memory.
This change add a large-reloc option to generate 64-bit unsigned integers.
It can be used when the kernel plan to go below the to
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/entry/entry_64.S | 2
Replace the %c constraint with %P. The %c is incompatible with PIE
because it implies an immediate value whereas %P reference a symbol.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
if PIE is enabled, switch the paravirt assembly constraints to be
compatible. The %c/i constrains generate smaller code so is kept by
default.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garni
Change assembly to use the new _ASM_GET_PTR macro instead of _ASM_MOV for
the assembly to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/include/asm/pm-t
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/crypto/aes-x86_64-as
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/power/hibernate_asm_
Add the CONFIG_X86_PIE option which builds the kernel as a Position
Independent Executable (PIE). The kernel is currently build with the
mcmodel=kernel option which forces it to stay on the top 2G of the
virtual address space. With PIE, the kernel will be able to move below
the -2G limit increasing
With PIE support and KASLR extended range, the modules may be further
away from the kernel than before breaking mcmodel=kernel expectations.
Add an option to build modules with mcmodel=large. The modules generated
code will make no assumptions on placement in memory.
Despite this option, modules
Add a new CONFIG_RANDOMIZE_BASE_LARGE option to benefit from PIE
support. It increases the KASLR range from 1GB to 3GB. The new range
stars at 0x just above the EFI memory region. This
option is off by default.
The boot code is adapted to create the appropriate page table spanning
Perpcu uses a clever design where the .percu ELF section has a virtual
address of zero and the relocation code avoid relocating specific
symbols. It makes the code simple and easily adaptable with or without
SMP support.
This design is incompatible with PIE because generated code always try to
acc
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Early at boot, the kernel is mapped at a temporary address while preparing
the page table. To know the changes needed for the page table with KASLR,
the boot code calculate the difference betwe
These patches make the changes necessary to build the kernel as Position
Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below
the top 2G of the virtual address space. It allows to optionally extend the
KASLR randomization range from 1G to 3G.
Thanks a lot to Ard Biesheuvel &
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible. The new __ASM_GET_PTR_PRE macro is used to
get the address of a symbol on both 32 and 64-bit with PIE support.
Position Independent Executable (PIE) support will allow to extended the
KASLR ran
Add a new _ASM_GET_PTR macro to fetch a symbol address. It will be used
to replace "_ASM_MOV $, %dst" code construct that are not compatible
with PIE.
Signed-off-by: Thomas Garnier
---
arch/x86/include/asm/asm.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/x86/include/
Change the assembly code to use the new _ASM_GET_PTR macro which get a
symbol reference while being PIE compatible. Modify the RELOC macro that
was using an assignment generating a non-relative reference.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/kernel/acpi/wakeup_6
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible. Use the new _ASM_GET_PTR macro instead of
the 'mov $symbol, %dst' construct to not have an absolute reference.
Position Independent Executable (PIE) support will allow to extended the
KASLR ran
Provide an option to default visibility to hidden except for key
symbols. This option is disabled by default and will be used by x86_64
PIE support to remove errors between compilation units.
Signed-off-by: Thomas Garnier
---
arch/x86/boot/boot.h | 2 +-
arch/x86/include/asm/setup.h
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/kernel/relocate_kern
Replace the %c constraint with %P. The %c is incompatible with PIE
because it implies an immediate value whereas %P reference a symbol.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
By default PIE generated code create only relative references so _text
points to the temporary virtual address. Instead use a global variable
so the relocation is done as expected.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memo
On Mon, 3 Jul 2017, Stefano Stabellini wrote:
> On Mon, 3 Jul 2017, Owen Smith wrote:
> > Backends set "feature-raw-pointer" if its capable of reporting
> > absolute positions without scaling the coordinates to screen
> > size. This should be set during the backend init.
> > Frontends set "request-
From: Igor Druzhinin
This new call is trying to update a requested map cache entry
according to the changes in the physmap. The call is searching
for the entry, unmaps it and maps again at the same place using
a new guest address. If the mapping is dummy this call will
make it real.
This functio
Commit 090fa1c8 "add support for unplugging NVMe disks..." extended the
existing disk unplug flag to cover NVMe disks as well as IDE and SCSI.
The recent thread on the xen-devel mailing list [1] has highlighted that
this is not desirable behaviour: PV frontends should be able to distinguish
NVMe d
From: Igor Druzhinin
Non-functional change.
Signed-off-by: Igor Druzhinin
Reviewed-by: Stefano Stabellini
Reviewed-by: Paul Durrant
---
hw/i386/xen/xen-hvm.c | 57 ---
1 file changed, 31 insertions(+), 26 deletions(-)
diff --git a/hw/i386/xen/
From: Xiong Zhang
In igd passthrough environment, guest could only access opregion at the
first bootup time. Once guest shutdown, later guest couldn't access
opregion anymore.
This is because qemu set emulated guest opregion base address to host
register. Later guest get a wrong host opregion bas
From: Peter Maydell
Check the return status of the xen_host_pci_get_* functions we call in
xen_pt_msix_init(), and fail device init if the reads failed rather than
ploughing ahead. (Spotted by Coverity: CID 777338.)
Signed-off-by: Peter Maydell
Reviewed-by: Stefano Stabellini
Signed-off-by: St
From: Igor Druzhinin
Dummys are simple anonymous mappings that are placed instead
of regular foreign mappings in certain situations when we need
to postpone the actual mapping but still have to give a
memory region to QEMU to play with.
This is planned to be used for restore on Xen.
Signed-off-
From: Igor Druzhinin
If we have a system with xenforeignmemory_map2() implemented
we don't need to save/restore physmap on suspend/restore
anymore. In case we resume a VM without physmap - try to
recreate the physmap during memory region restore phase and
remap map cache entries accordingly. The
t tags/xen-20170718-tag
for you to fetch changes up to 331b5189d756d431b1d18ae7097527ba3d3ea809:
xen: don't use xenstore to save/restore physmap anymore (2017-07-18 14:16:52
-0700)
On Tue, 11 Jul 2017, Alexey G wrote:
> Under certain circumstances normal xen-mapcache functioning may be broken
> by guest's actions. This may lead to either QEMU performing exit() due to
> a caught bad pointer (and with QEMU process gone the guest domain simply
> appears hung afterwards) or actua
On Mon, 10 Jul 2017, Igor Druzhinin wrote:
> If we have a system with xenforeignmemory_map2() implemented
> we don't need to save/restore physmap on suspend/restore
> anymore. In case we resume a VM without physmap - try to
> recreate the physmap during memory region restore phase and
> remap map c
On Mon, 10 Jul 2017, Igor Druzhinin wrote:
> This new call is trying to update a requested map cache entry
> according to the changes in the physmap. The call is searching
> for the entry, unmaps it and maps again at the same place using
> a new guest address. If the mapping is dummy this call will
On Mon, Jul 17, 2017 at 01:54:19PM +, Christian Lindig wrote:
>
> > On 17. Jul 2017, at 13:38, Andrew Cooper wrote:
> >
> > It turns out that Xapi has a library function using it, but that
> > function is dead so can be removed.
>
> I am fine with the removal of the OCaml bindings and the p
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> This patch finally adds the support for vuart console. It adds
> two new fields in the console initialization:
>
> - optional
> - prefer_gnttab
>
> optional flag tells whether the console is optional.
>
> prefer_gnttab tells whether the ring buffer
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> This patch adds the support for multiple consoles and introduces the iterator
> functions to operate on multiple consoles.
>
> This patch is in preparation to support a new vuart console.
>
> Signed-off-by: Bhupinder Thakur
> ---
> CC: Ian Jackson
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> This patch introduces a console_close_evtchn console_cleanup function. This
> function
> closes the console event channel.
>
> Signed-off-by: Bhupinder Thakur
Reviewed-by: Stefano Stabellini
> ---
> CC: Ian Jackson
> CC: Wei Liu
> CC: Stefano
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> This patch introduces a console_open_log console_cleanup function. This
> function
> opens the console log file.
>
> Signed-off-by: Bhupinder Thakur
> ---
> CC: Ian Jackson
> CC: Wei Liu
> CC: Stefano Stabellini
> CC: Julien Grall
>
> Changes s
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> This patch introduces a new console_cleanup function. This function
> frees up the console resources.
>
> Signed-off-by: Bhupinder Thakur
> ---
> CC: Ian Jackson
> CC: Wei Liu
> CC: Stefano Stabellini
> CC: Julien Grall
>
> Changes since v5:
> -
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> This patch introduces a new handle_console_tty function. This function
> performs read/write from/to console tty.
>
> Signed-off-by: Bhupinder Thakur
Reviewed-by: Stefano Stabellini
> ---
> CC: Ian Jackson
> CC: Wei Liu
> CC: Stefano Stabellini
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> This patch introduces a new handle_console_ring function. This function
> reads the data from the ring buffer on receiving an event.
>
> Signed-off-by: Bhupinder Thakur
Reviewed-by: Stefano Stabellini
> ---
> CC: Ian Jackson
> CC: Wei Liu
> CC:
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> This patch introduces a new add_console_tty_fd function. This function
> adds the tty fd to the list of polled fds.
>
> Signed-off-by: Bhupinder Thakur
Reviewed-by: Stefano Stabellini
> ---
> CC: Ian Jackson
> CC: Wei Liu
> CC: Stefano Stabelli
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> This patch introduces a new buffer_available function to check if
> more data is allowed to be buffered.
>
> Signed-off-by: Bhupinder Thakur
Reviewed-by: Stefano Stabellini
> ---
> CC: Ian Jackson
> CC: Wei Liu
> CC: Stefano Stabellini
> CC: J
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> Add a new domctl API to initialize vpl011. It takes the GFN and console
> backend domid as input and returns an event channel to be used for
> sending and receiving events from Xen.
>
> Xen will communicate with xenconsole using GFN as the ring buffer
On Mon, 17 Jul 2017, Bhupinder Thakur wrote:
> Add emulation code to emulate read/write access to pl011 registers
> and pl011 interrupts:
>
> - Emulate DR read/write by reading and writing from/to the IN
> and OUT ring buffers and raising an event to the backend when
> there is dat
On 18/07/17 15:53, Felix Schmoll wrote:
> Implement reading from PV console. Making use of polling.
>
> Signed-off-by: Felix Schmoll
> ---
> common/console.c | 22 ++
> include/xtf/console.h | 2 ++
> 2 files changed, 24 insertions(+)
>
> diff --git a/common/console.c b/
flight 111982 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111982/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 4b3fe14e291109d6a1fc140c039e8a638672070a
baseline version:
xtf d94ba594f2e680dc4f1d10
1. Motivation and Description
Virtual machines use grant table hypercalls to setup a share page for
inter-VMs communications. These hypercalls are used by all PV
protocols today. However, very
Hi,
On 18/07/17 16:29, Wei Liu wrote:
On Tue, Jul 18, 2017 at 05:11:30PM +0530, vijay.kil...@gmail.com wrote:
[...]
diff --git a/xen/common/numa.c b/xen/common/numa.c
new file mode 100644
index 000..0381f1b
--- /dev/null
+++ b/xen/common/numa.c
@@ -0,0 +1,487 @@
+/*
+ * Common NUMA handling
Hi Vijay,
On 18/07/17 12:41, vijay.kil...@gmail.com wrote:
From: Vijaya Kumar K
Right now CONFIG_NUMA is not enabled for ARM and
existing code in asm-arm/numa.h is for !CONFIG_NUMA.
Hence put this code under #ifndef CONFIG_NUMA.
This help to make this changes work when CONFIG_NUMA
is not enab
On 18/07/17 17:25, Julien Grall wrote:
Hi,
On 18/07/17 12:41, vijay.kil...@gmail.com wrote:
From: Vijaya Kumar K
CONFIG_NUMA is defined in xen/drivers/acpi/Kconfig.
Move to common/Kconfig and enabled by default.
Also, NUMA feature uses PDX for physical address to
memory node mapping. Hence
Hi,
On 18/07/17 12:41, vijay.kil...@gmail.com wrote:
From: Vijaya Kumar K
Introduce NR_NODES config option to specify number
of NUMA nodes supported. By default value is set at
64 for x86 and 8 for arm. Dropped NODES_SHIFT macro.
Also move NR_NODE_MEMBLKS from asm-x86/acpi.h to xen/numa.h
Si
Hi,
On 18/07/17 16:29, Wei Liu wrote:
On Tue, Jul 18, 2017 at 05:11:23PM +0530, vijay.kil...@gmail.com wrote:
From: Vijaya Kumar K
Introduce NR_NODES config option to specify number
of NUMA nodes supported. By default value is set at
64 for x86 and 8 for arm. Dropped NODES_SHIFT macro.
Also
On Mon, 17 Jul 2017, Roger Pau Monné wrote:
> Hello,
>
> I didn't actually take notes, so this is from the top of my head. If
> anyone took notes or remember something different, please feel free to
> correct it.
>
> This is the output from the PVH toolstack interface session. The
> participants
On Tue, Jul 18, 2017 at 9:25 AM, Adrian Pop wrote:
> From: Vlad Ioan Topan
>
> The default value for the "suppress #VE" bit set by set_mem_access()
> currently depends on whether the call is made from the same domain (the
> bit is set when called from another domain and cleared if called from
> t
On Tue, Jul 18, 2017 at 9:25 AM, Adrian Pop wrote:
> Introduce a new hvmop, HVMOP_altp2m_set_suppress_ve, which allows a
> privileged domain to change the value of the #VE suppress bit for a
> page.
>
> Add a libxc wrapper for invoking this hvmop.
>
> Signed-off-by: Adrian Pop
> Acked-by: Wei Liu
Signed-off-by: Anthony PERARD
---
arch/x86/include/arch/apic.h | 3 +++
tests/vlapic-timer/main.c| 40
2 files changed, 43 insertions(+)
diff --git a/arch/x86/include/arch/apic.h b/arch/x86/include/arch/apic.h
index 4cb262d..0f48df1 100644
--- a/arch
Hi,
Check the behavior of the vLAPIC timer emulation.
This list of check works on baremetal if one managed to runned it (I did manual
testing by coping this xtf tests into xen), but Xen emulation vlapic does not
behave like baremetal, so this XTF tests would fail at first, until a fix for
Xen tha
Start by testing one-shot and periodic timer modes.
The behavior of TMICT and TMCCT while switching between periodic and
one-shot timer modes check in this test is mostly base on observation of
baremetal. Intel SDM gives little details about it.
Signed-off-by: Anthony PERARD
---
arch/x86/includ
Signed-off-by: Anthony PERARD
---
arch/x86/include/arch/apic.h | 1 +
arch/x86/include/arch/cpuid.h | 1 +
arch/x86/include/arch/lib.h | 9 ++
arch/x86/include/arch/msr-index.h | 1 +
tests/vlapic-timer/main.c | 67 +++
5 files ch
flight 111963 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111963/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 10 windows-install fail REGR. vs. 111765
test-amd64-i386-x
**Dear All,
During the developers summit a Shared Coprocessor Framework (SCF)
concept was presented. Noticeable interest from community was discovered
during discussions. So this is a call for all interested parties to
collect a feedback and setup a collaboration.
There are several topics I
The description in the Intel SDM of how the divide configuration
register is used: "The APIC timer frequency will be the processor's bus
clock or core crystal clock frequency divided by the value specified in
the divide configuration register."
Observation of baremetal shown that when the TDCR is
There should not be any functionality change with this patch.
This function is used when the APIC_TMICT register is updated.
vlapic_update_timer is introduce as it will be use also when the
registers APIC_LVTT and APIC_TDCR are updated.
Signed-off-by: Anthony PERARD
---
xen/arch/x86/hvm/vlapic
Hi,
When developing PVH for OVMF, I've used the lapic timer. It turns out that the
way it is used by OVMF did not work with Xen [1]. I tried to find out how
real-hw behave, and write a XTF tests [2]. And this patch series tries to fix
the behavior of the vlapic timer.
The OVMF driver for the APIC
If we take TSC-deadline mode timer out of the picture, the Intel SDM
does not say that the timer is disable when the timer mode is change,
either from one-shot to periodic or vice versa.
After this patch, the timer is no longer disarmed on change of mode, so
the counter (TMCCT) keeps counting down
Dear Ajeesh,
I'm just courious, are you using an updated wiki [1]?
[1]
https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X
--
*Andrii Anisov*
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.o
Dear Ajeesh,
On 18.07.17 17:10, ajmalmalib4u wrote:
I am using R-Car H3 hardware. ie. R-Car H3 Salvator-X. I am running
Xen with Poky linux as Dom0 and DomU. Would i be able to run Xen with
the same setup on R-Car H3 Starter Kit?
You should have to apply appropriate changes to h3ulcb device tre
flight 111966 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/111966/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 111915
test-armhf-armhf-libvirt-xsm 14 saveresto
From: Andrii Anisov
Both Renesas R-Car Gen2(ARM32) and Gen3(ARM64) are utilizing SCIF IP,
so make its serial driver built by default for ARM.
Signed-off-by: Andrii Anisov
---
xen/drivers/char/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xen/drivers/char/Kconf
On 07/18/2017 12:12 PM, Juergen Gross wrote:
> On 18/07/17 18:08, Boris Ostrovsky wrote:
>> On 07/10/2017 04:10 AM, Juergen Gross wrote:
>>> When setting up the Xenstore watch for the memory target size the new
>>> watch will fire at once. Don't try to reach the configured target size
>>> by onlini
On 18/07/17 16:29, Wei Liu wrote:
On Tue, Jul 18, 2017 at 05:11:33PM +0530, vijay.kil...@gmail.com wrote:
From: Vijaya Kumar K
Introduce new api device_tree_type_matches() to check for
device type. Also export device_tree_get_u32() and
device_tree_node_compatible()
These functions are later
Hi,
On 18/07/17 12:41, vijay.kil...@gmail.com wrote:
From: Vijaya Kumar K
CONFIG_NUMA is defined in xen/drivers/acpi/Kconfig.
Move to common/Kconfig and enabled by default.
Also, NUMA feature uses PDX for physical address to
memory node mapping. Hence make HAS_PDX dependent
for NUMA.
Signed-o
Hi,
On 18/07/17 12:41, vijay.kil...@gmail.com wrote:
This patch is tested on Thunderx platform.
No changes are made to x86 implementation only code is sanitized
and refactored. Hence only compilation tested for x86.
This series is posted as RFC for the reason that it is not tested
on x86. Reque
On Tue, 18 Jul 2017, Zhongze Liu wrote:
> Hi Julien,
>
> After our discussion during the summit, I have revised my plan, but
> I'm still working on it and haven't sent it to the ML yet.
> I'm planning to send a new version of my proposal together with the
> parsing code later so that I could refer
On 18/07/17 18:08, Boris Ostrovsky wrote:
> On 07/10/2017 04:10 AM, Juergen Gross wrote:
>> When setting up the Xenstore watch for the memory target size the new
>> watch will fire at once. Don't try to reach the configured target size
>> by onlining new memory in this case, as the current memory s
On 07/10/2017 04:10 AM, Juergen Gross wrote:
> When setting up the Xenstore watch for the memory target size the new
> watch will fire at once. Don't try to reach the configured target size
> by onlining new memory in this case, as the current memory size will
> be smaller in almost all cases due t
On Tue, Jul 18, 2017 at 02:38:14PM +0100, Wei Liu wrote:
> On Fri, Jul 07, 2017 at 10:00:01AM -0400, Konrad Rzeszutek Wilk wrote:
> > >
> > > 1. PV PCI passthrough is done via pciback, which means the physical
> > >device is assigned to the driver domain. All events to / from the
> > >gues
On Tue, Jul 18, 2017 at 05:11:33PM +0530, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> Introduce new api device_tree_type_matches() to check for
> device type. Also export device_tree_get_u32() and
> device_tree_node_compatible()
>
> These functions are later used for parsing NUMA in
On Tue, Jul 18, 2017 at 05:11:27PM +0530, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> Add accessors for nodes[] and other static variables and
> use those accessors. These variables are later accessed
> outside the file when the code made generic in later
> patches. However the codin
1 - 100 of 263 matches
Mail list logo
