>>> On 30.01.16 at 02:47, wrote:
> On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
>> (re-adding xen-devel)
>>
>> >>> On 26.01.16 at 12:28, wrote:
>> > Iommu=0 let the whole Qubes system work, without enforcing hardware
>> > compartimentalisation (iommu is enforced in software mode)
On 01/02/16 08:53, Jan Beulich wrote:
On 01.02.16 at 05:54, wrote:
>> On 29/01/16 17:46, Jan Beulich wrote:
>> On 29.01.16 at 17:26, wrote:
On Fri, Jan 29, 2016 at 09:00:15AM -0700, Jan Beulich wrote:
On 29.01.16 at 16:30, wrote:
>> I am hoping the maintainers can guid
>>> On 29.01.16 at 18:09, wrote:
> On 29/01/16 16:53, Jan Beulich wrote:
> On 29.01.16 at 15:02, wrote:
>>> On 29/01/16 14:57, Egger, Christoph wrote:
On 29/01/16 14:24, Jan Beulich wrote:
> Christoph,
>
> in commit dd6de3ab99 ("Implement Nested-on-Nested") you added
> co
>>> On 01.02.16 at 09:03, wrote:
> On 01/02/16 08:53, Jan Beulich wrote:
> On 01.02.16 at 05:54, wrote:
>>> On 29/01/16 17:46, Jan Beulich wrote:
>>> On 29.01.16 at 17:26, wrote:
> On Fri, Jan 29, 2016 at 09:00:15AM -0700, Jan Beulich wrote:
> On 29.01.16 at 16:30, wrote:
>>
On 01/02/16 09:04, Jan Beulich wrote:
>>> This, otoh, reads as if you imply we intercept the L2's INVLPG.
>>> Yet the INVLPG intercept gets cleared when the domain uses
>>> NPT (and your original change also didn't alter any intercept
>>> settings). Hence I'm still lost how hap_invlpg() can be reac
>>> On 01.02.16 at 09:14, wrote:
> On 01/02/16 09:04, Jan Beulich wrote:
This, otoh, reads as if you imply we intercept the L2's INVLPG.
Yet the INVLPG intercept gets cleared when the domain uses
NPT (and your original change also didn't alter any intercept
settings). Hence I'm
XRSTORS unconditionally faults when xcomp_bv has bit 63 clear. Instead
of just fixing this issue, overhaul the fault recovery code, which -
one of the many mistakes made when xstate support got introduced - was
blindly mirroring that accompanying FXRSTOR, neglecting the fact that
XRSTOR{,S} aren't
When mapping large BARs (e.g. the frame buffer of a graphics card) the
overhead of establishing such mappings using only 4k pages has,
particularly after the XSA-125 fix, become unacceptable. Alter the
XEN_DOMCTL_memory_mapping semantics once again, so that there's no
longer a fixed amount of guest
From: Vijaya Kumar K
Store the number of lpis allocated per domain in vgic structure
Signed-off-by: Vijaya Kumar K
---
v8: - Updated commit message and added comments
- Removed initialization of vgic.nr_lpis to zero
v7: - Change commit message.
- Store only nr_lpis per domain in vgic st
From: Vijaya Kumar K
GICD_TYPER register definitions are defined as GICD_TYPE.
Rename all GICD_TYPE_* as GICD_TYPER_*
Signed-off-by: Vijaya Kumar K
---
xen/arch/arm/gic-hip04.c |4 ++--
xen/arch/arm/gic-v2.c |6 +++---
xen/arch/arm/gic-v3.c |2 +-
x
From: Vijaya Kumar K
Call domain specific ITS initialization and introduce
callback in vgic for domain free
Signed-off-by: Vijaya Kumar K
---
v7: - Deprecate use of gic_lpi_supported and instead use
vgic_v3_hw.lpi_support
v6: - Moved vits_domain_free() out of this patch
---
xen/arch/arm/
From: Vijaya Kumar K
This patch introduces virtual ITS driver with following
functionality
- Introduces helper functions to manage device table and
ITT table in guest memory
- Helper function to handle virtual ITS devices assigned
to domain
Signed-off-by: Vijaya Kumar K
Reviewed-by: Jul
From: Vijaya Kumar K
Introduce vgic_is_lpi_supported() helper function
to know virtual ITS availability for a domain
Signed-off-by: Vijaya Kumar K
---
v8: - Dropped its_enabled field
v7: - its_enabled field is added to vgic structure
---
xen/arch/arm/vgic.c|5 +
xen/include/asm
From: Vijaya Kumar K
NR_IRQS represents the number of lines (i.e SGIs, PPIs and SPIs).
With the introduction of LPIs, NR_IRQs is renamed to NR_ITLINES.
Similarly vgic_num_irqs() is renamed as vgic_num_irq_lines().
Signed-off-by: Vijaya Kumar K
Reviewed-by: Julien Grall
---
v7: - Renamed NR_LIN
From: Vijaya Kumar K
Helper function gic_is_lpi() is used to find
if irq is lpi or not. For GICv2 platforms this function
returns number of irq ids which represents only number of line irqs.
For GICv3 platform irq ids are calculated from nr_lpis if
HW supports LPIs
Signed-off-by: Vijaya Kumar K
From: Vijaya Kumar K
Implement hw_irq_controller callbacks required to
handle LPIs.
Signed-off-by: Vijaya Kumar K
Reviewed-by: Julien Grall
---
v8: - Removed const before hw_irq_controller for lpis
v7: - Split this patch into two. In this patch implement
only hw_irq_controller callbacks
From: Vijaya Kumar K
Add APIs to add devices to RB-tree, assign and remove
devices to domain.
Signed-off-by: Vijaya Kumar K
---
v8: - Merged its_free_msi_descs() with its_discard_lpis
- Dropped extra spin_unlock() in its_assign_device()
- Dropped check on device domain to be dom0 in ass
From: Vijaya Kumar K
Parse host dt and generate ITS node for Dom0.
ITS node resides inside GIC node so when GIC node
is encountered look for ITS node.
Signed-off-by: Vijaya Kumar K
---
v7: - Check on return value
v6: - Introduced get_its_phandle in gic_hw_ops
- Removed make_hwdom_its_dt_nod
From: Vijaya Kumar K
ITS initialization required for all PCI devices in
ThunderX platform are done by calling from specific
mapping function.
This patch can be reverted once XEN PCI passthrough
framework for arm64 is in available.
For now all the PCI devices are assigned to Dom0
Signed-off-by:
From: Vijaya Kumar K
Define msi_desc structure for arm and introduce
helper functions to access msi_desc member variables.
Signed-off-by: Vijaya Kumar K
Reviewed-by: Julien Grall
---
xen/arch/arm/gic-v3-its.c | 28
xen/arch/arm/irq.c| 12 ++
From: Vijaya Kumar K
Initialize physical ITS if HW supports LPIs.
Signed-off-by: Vijaya Kumar K
---
v8: - Rename lpi_support to its_support.
- Removed its command line parameter.
- Dropped its_enabled global variable.
v7: - Export lpi support information to vgic-v3 driver from gic-v3.
From: Vijaya Kumar K
Change callbacks gic_host_irq_type and gic_guest_irq_type
to gic_get_host_irq_type and gic_get_guest_irq_type
in gic_hw_operations, which returns hw_irq_controller based
on irq type (SPI or LPI).
Signed-off-by: Vijaya Kumar K
CC: Zoltan Kiss
Reviewed-by: Julien Grall
---
From: Vijaya Kumar K
The linux driver is based on 4.1 with below commit id
591e5bec13f15feb13fc445b6c9c59954711c4ac
Only following code from Linux ITS driver is ported
and compiled
- LPI initialization
- ITS configuration code
- Physical command queue management
- ITS command building
Also
From: Vijaya Kumar K
bitmap_find_next_zero_area helper function will be used
by physical ITS driver. This is imported from linux 4.2
Signed-off-by: Vijaya Kumar K
Acked-by: Jan Beulich
CC: Ian Campbell
CC: Ian Jackson
CC: Jan Beulich
CC: Keir Fraser
CC: Tim Deegan
---
v5: Ported from Linu
From: Vijaya Kumar K
Emulate LPI related changes to GICR registers
Signed-off-by: Vijaya Kumar K
---
v8: - Updated GICR_PROPBASER and GICR_PENDBASER only on enabling
LPIs and added 32/64 bit reg access
- Allocated LPI property table of size supported by Xen.
- Moved LPI property t
From: Vijaya Kumar K
Allocate dynamically pending_lpi descriptors for LPIs
Signed-off-by: Vijaya Kumar K
---
v8: - Dropped HAS_GICV3 config switch around pending_lpis[]
---
xen/arch/arm/vgic-v3-its.c |9 +
xen/arch/arm/vgic.c | 12 +---
xen/include/asm-arm/doma
From: Vijaya Kumar K
ITS translation space contains GITS_TRANSLATER register
which is written by device to raise LPI. This space needs
to mapped to every domain address space for all physical
ITS available,so that device can access GITS_TRANSLATER
register using SMMU.
Signed-off-by: Vijaya Kumar
From: Vijaya Kumar K
Helper functions to manage its devices using RB-tree
are introduced in physical ITS driver.
This is global list of all the devices.
Signed-off-by: Vijaya Kumar K
---
v8: - Added assert on lock in its_remove_device()
- Dropped Ack's from Ian and Julien
v7: - Introduce i
From: Vijaya Kumar K
Export physical ITS information to virtual ITS driver
Signed-off-by: Vijaya Kumar K
---
v8: - eventID_bits and devID_bits are made its node specific.
Max of all the nodes is considered
- Moved assert on eventID_bits from its_assign_device()
to its_add_device
From: Vijaya Kumar K
log2 helper apis are ported from linux from
commit 13c07b0286d340275f2d97adf085cecda37ede37
(linux/log2.h: Fix rounddown_pow_of_two(1))
Changes made for xen are:
- Only required functionality is retained
- Replace fls_long with flsl
Signed-off-by: Vijaya Kumar K
Acked-b
From: Vijaya Kumar K
Allocate dynamically irq descriptors for LPIs
Signed-off-by: Vijaya Kumar K
---
v8: - Use gic_nr_irq_ids() instead of nr_lpis
v6: - Add separate patch for irq_pending structures
- renamed and moved is_domain_lpi to vgic
- Updated __irq_to_domain
---
xen/arch/arm/gi
From: Vijaya Kumar K
nr_cpu_ids for arm platforms is incorrectly set to NR_CPUS
irrespective of the number of cpus supported by platform.
Signed-off-by: Vijaya Kumar K
Reviewed-by: Julien Grall
---
v6: - Updated nr_cpu_ids in setup.c instead of creating
a helper function
---
xen/arch/ar
From: Vijaya Kumar K
Allocate and initialize irq descriptor for LPIs and
route LPIs to guest
For LPIs deactivation is not required. Hence
GICH_LR.HW is not required to set.
Signed-off-by: Vijaya Kumar K
---
v7: - Subtract 8192 from irq number to index to lpi property
table to read priori
From: Vijaya Kumar K
This is based on DraftG version
http://xenbits.xen.org/people/ianc/vits/draftG.pdf
Following major features are supported
- GICv3 ITS support for arm64 platform
- Only Dom0 is supported. For DomU pci passthrough feature
is required.
Major Changes in v8:
- Rebased to l
From: Vijaya Kumar K
Emulate GITS* registers
Signed-off-by: Vijaya Kumar K
---
v8: - Fixed GITS_BASER0 value.
- Added comments for GITS_BASER0.
- Support 32/64 bit access for GITS_BASER0 and GITS_CBASER.
- s/vits->ctrl/vits->ctlr/
- Used VREG{64,32} and VRANGE{64,32} macros
v7:
From: Vijaya Kumar K
Enable compilation of pITS driver.
Signed-off-by: Vijaya Kumar K
---
xen/arch/arm/Makefile |1 +
1 file changed, 1 insertion(+)
diff --git a/xen/arch/arm/Makefile b/xen/arch/arm/Makefile
index 9982a93..4970641 100644
--- a/xen/arch/arm/Makefile
+++ b/xen/arch/arm/Make
From: Vijaya Kumar K
Add Virtual ITS command processing support to Virtual ITS driver
Signed-off-by: Vijaya Kumar K
Reviewed-by: Julien Grall
---
v8: - Fixed coding styles
v7: - Moved is_valid_collection() declaration to vits.h
- Added check for number of vcpus of a domain in
vits_do
On Sat, 2016-01-30 at 04:19 +, osstest service owner wrote:
> flight 79397 linux-3.14 real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/79397/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-amd64-rumpuserxe
On Sun, 2016-01-31 at 14:02 +, osstest service owner wrote:
> flight 79465 linux-3.10 real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/79465/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-i386-rumpuserxen
On 01/02/16 10:00, Jan Beulich wrote:
On 01.02.16 at 09:14, wrote:
>> On 01/02/16 09:04, Jan Beulich wrote:
> This, otoh, reads as if you imply we intercept the L2's INVLPG.
> Yet the INVLPG intercept gets cleared when the domain uses
> NPT (and your original change also didn't al
On Sun, 2016-01-31 at 09:30 -0700, Tamas K Lengyel wrote:
>
>
> On Sun, Jan 31, 2016 at 2:07 AM, Razvan Cojocaru om> wrote:
> > This patch covers modifications to xen/arch/*/vm_event.c, in order
> > to include ARM vm_event maintainership.
> >
> > Signed-off-by: Razvan Cojocaru
> Once vm_event.
On Fri, 2016-01-29 at 10:30 -0500, Konrad Rzeszutek Wilk wrote:
> - Deal with documentation? I removed the allowsuperpage from
> documentation
> but perhaps it should just mention deprecated?
"deprecated" means "still available but use is discouraged". Since AIUI you
really are removing PV sup
At 18:20 + on 29 Jan (1454091618), Andrew Cooper wrote:
> Signed-off-by: Andrew Cooper
Acked-by: Tim Deegan
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
>>> On 01.02.16 at 10:41, wrote:
> On 01/02/16 10:00, Jan Beulich wrote:
> On 01.02.16 at 09:14, wrote:
>>> On 01/02/16 09:04, Jan Beulich wrote:
>> This, otoh, reads as if you imply we intercept the L2's INVLPG.
>> Yet the INVLPG intercept gets cleared when the domain uses
>> NPT
(Cc Roger)
On Sun, Jan 31, 2016 at 01:27:23PM -0800, PGNet Dev wrote:
> I run Xen 4.6 Dom0
>
> rpm -qa | egrep -i "kernel-default-4|xen-4"
> kernel-default-devel-4.4.0-8.1.g9f68b90.x86_64
> xen-4.6.0_08-405.1.x86_64
>
> My guests are currently HVM in PVHVM mode;
flight 38718 distros-debian-sid real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38718/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-amd64-sid-netboot-pvgrub 10 guest-start fail blocked in 38654
test-armhf-armhf-ar
On Fri, Jan 29, 2016 at 10:16:04AM -0600, Doug Goldstein wrote:
> Hi all,
>
> I agree to the conditions in the Xen Project Security [1] and Coverity
> [2] Contribution guidelines.
>
> I have been a Gentoo Linux developer since 2001 and involved with
> downstream packaging of virtualization produc
El 31/01/16 a les 22.27, PGNet Dev ha escrit:
> I run Xen 4.6 Dom0
>
> rpm -qa | egrep -i "kernel-default-4|xen-4"
> kernel-default-devel-4.4.0-8.1.g9f68b90.x86_64
> xen-4.6.0_08-405.1.x86_64
Are your kernels compiled with CONFIG_PVH enabled?
> My guests are currently HVM in
El 01/02/16 a les 4.47, PGNet Dev ha escrit:
> In any case, the !st issue, prior to any guest being launched, simply
> adding
>
>> @ GRUBG cfg
>>
>> -GRUB_CMDLINE_XEN=" ..."
>> +GRUB_CMDLINE_XEN=" dom0pvh ..."
Does your kernel support PVH mode (ie: CONFIG_PVH enabled?)
> causes boot fail
You have two "libxl" in subject line.
On Fri, Jan 29, 2016 at 10:30:46AM -0500, Konrad Rzeszutek Wilk wrote:
> The last bastion of users is moving away from needing
> this.
>
> Please note that there was an partial removal by
> c/s 9b3c6b13e0c085ceb53210f8e682a073096b94fa
> "libxc: remove superpa
On Thu, Jan 28, 2016 at 11:58:25AM +0100, Vitaly Kuznetsov wrote:
> We don't need to free anything extra from Dom0 in order to perform soft
> reset. It can also fail soft reset if it happens that we don't have this
> memory (which we don't need) available.
>
> Signed-off-by: Vitaly Kuznetsov
Ack
This email only tracks big items for xen.git tree. Please reply for items you
woulk like to see in 4.7 so that people have an idea what is going on and
prioritise accordingly.
You're welcome to provide description and use cases of the feature you're
working on.
= Timeline =
We now adopt a fixed
On Sat, 2016-01-30 at 14:18 +0100, Tommi Airikka wrote:
>
>
> On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk e.com> wrote:
> > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote:
> > > Xen developers,
> > >
> > > After an upgrade of my Debian Jessie dom0 and domUs, my passthro
>>> On 01.02.16 at 08:42, wrote:
> The X86 domain structure already occupied PAGE_SIZE (4096).
>
> Looking @ the memory layout of the structure, we could see that
> overall most was occupied by (used the pahole tool on domain.o):
> * sizeof(domain.arch) = sizeof(arch_domain) = 3328 bytes.
> * s
On 2/1/2016 12:47 PM, Jan Beulich wrote:
On 01.02.16 at 08:42, wrote:
The X86 domain structure already occupied PAGE_SIZE (4096).
Looking @ the memory layout of the structure, we could see that
overall most was occupied by (used the pahole tool on domain.o):
* sizeof(domain.arch) = sizeof(ar
Nice work, Andy.
On Thu, Jan 28, 2016 at 06:31:13PM -0800, Andy Lutomirski wrote:
> This switches virtio to use the DMA API on Xen and if requested by
> module option.
>
> This fixes virtio on Xen, and it should break anything because it's
> off by default on everything except Xen PV on x86.
>
On Thu, Jan 28, 2016 at 01:58:07PM -0700, Tamas K Lengyel wrote:
> The altp2m subsystem in its current form uses its own HVMOP hypercall to set
> mem_access permissions, duplicating some of the code already present for
> setting regular mem_access permissions. In this patch we consolidate the two
>
On 01/02/16 07:42, Corneliu ZUZU wrote:
> The X86 domain structure already occupied PAGE_SIZE (4096).
>
> Looking @ the memory layout of the structure, we could see that
> overall most was occupied by (used the pahole tool on domain.o):
> * sizeof(domain.arch) = sizeof(arch_domain) = 3328 bytes.
>
c/s 2d2f789 "tools: rename libxc's evtchn_port_or_error_t with an xc_
prefix" doesn't cater for older applications which have requested
XC_WANT_COMPAT_EVTCHN_API
Signed-off-by: Andrew Cooper
---
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/libxc/include/xenctrl_compat.h | 1 +
1 fil
On Mon, 2016-02-01 at 11:08 +, Andrew Cooper wrote:
> c/s 2d2f789 "tools: rename libxc's evtchn_port_or_error_t with an xc_
> prefix" doesn't cater for older applications which have requested
> XC_WANT_COMPAT_EVTCHN_API
I think we can safely assume that such apps are not also using xenevtchn.h
On Thu, 2016-01-28 at 18:31 -0800, Andy Lutomirski wrote:
> This is a kludge, but no one has come up with a a better idea yet.
> We'll introduce DMA API support guarded by vring_use_dma_api().
> Eventually we may be able to return true on more and more systems,
> and hopefully we can get rid of vri
On 01/02/16 09:13, Jan Beulich wrote:
> XRSTORS unconditionally faults when xcomp_bv has bit 63 clear. Instead
> of just fixing this issue, overhaul the fault recovery code, which -
> one of the many mistakes made when xstate support got introduced - was
> blindly mirroring that accompanying FXRSTO
On 2/1/2016 1:07 PM, Andrew Cooper wrote:
On 01/02/16 07:42, Corneliu ZUZU wrote:
The X86 domain structure already occupied PAGE_SIZE (4096).
Looking @ the memory layout of the structure, we could see that
overall most was occupied by (used the pahole tool on domain.o):
* sizeof(domain.arch)
This series replaces the current read-write lock implementation with
the queued read-write locks from Linux. These are fair; under
contention both readers and writers will be queued and obtain the lock
in FIFO order (due to the fairness of the internal ticket lock).
The implementation is all in C
From: Jennifer Herbert
In preparation for a replacement read-write lock implementation, move
the API and the per-cpu read-write locks into their own files.
Signed-off-by: Jennifer Herbert
Signed-off-by: David Vrabel
---
v3:
- fix XSM build
v2:
- new
---
xen/arch/x86/mm/mem_sharing.c | 1 +
From: Jennifer Herbert
The current rwlocks are write-biased and unfair. This allows writers
to starve readers in situations where there are many writers (e.g.,
p2m type changes from log dirty updates during domain save).
Replace the current implementation with queued read-write locks which use
On Fri, Jan 29, 2016 at 06:45:14PM +0800, Yu Zhang wrote:
> diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
> index 25507c7..0c19dee 100644
> --- a/tools/libxl/xl_cmdimpl.c
> +++ b/tools/libxl/xl_cmdimpl.c
> @@ -35,6 +35,7 @@
> #include
> #include
> #include
> +#include
>
Commit 599bad38cf added BUS_NOTIFY_REMOVED_DEVICE in order to allow
avoiding removal of IOMMU mappings before the driver actually got
unbound from the device. Naturally we should be using this too.
Signed-off-by: Jan Beulich
---
drivers/xen/pci.c |2 +-
1 file changed, 1 insertion(+), 1 dele
On 01/02/16 11:58, Jan Beulich wrote:
> Commit 599bad38cf added BUS_NOTIFY_REMOVED_DEVICE in order to allow
> avoiding removal of IOMMU mappings before the driver actually got
> unbound from the device. Naturally we should be using this too.
Because otherwise...? What happens if we don't make thi
On Mon, Feb 01, 2016 at 12:52:51AM -0700, Jan Beulich wrote:
> >>> On 30.01.16 at 15:38, wrote:
>
> > On 1/30/2016 12:33 AM, Jan Beulich wrote:
> > On 29.01.16 at 11:45, wrote:
> >>> --- a/xen/arch/x86/hvm/hvm.c
> >>> +++ b/xen/arch/x86/hvm/hvm.c
> >>> @@ -940,6 +940,8 @@ static int hvm_iore
>>> On 01.02.16 at 11:45, wrote:
> * xsave/xrtors support
> - Shuai Ruan
As per
http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg03264.html
and even more importantly
http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg03271.html
plus the lack of feedback from the orig
On Tue, Jan 26, 2016 at 04:30:57PM -0500, Konrad Rzeszutek Wilk wrote:
> The change is simple replace of raw strdup with a libxl variant.
> The benefit of that is the libxl variant has the extra
> behaviour of abort-on-alloc-fail - and will improve error handling.
>
> libxl_version_info is a bit o
On Tue, Jan 26, 2016 at 04:30:58PM -0500, Konrad Rzeszutek Wilk wrote:
> To hopefully clarify what it meant. Also point out that mechanism
> by which the return 1 value is done is via an intimate knowledge of the
> hypercall ABI (i.e. which register - eax - is the return value).
>
> Signed-off-by:
On Tue, Jan 26, 2016 at 04:30:59PM -0500, Konrad Rzeszutek Wilk wrote:
> The assert(info) is after quite a lot of manipulations
> on 'info' - which makes the assert pointless because if
> info was NULL it would have crashed earlier.
>
This sounds sensible.
> Remove it and make it an return. Also
On 02/01/2016 02:30 AM, Roger Pau Monné wrote:
Does your kernel support PVH mode (ie: CONFIG_PVH enabled?)
not CONFIG_PVH, but per http://wiki.xenproject.org/wiki/Linux_PVH
egrep \
"CONFIG_HYPERVISOR_GUEST=|CONFIG_PARAVIRT=|CONFIG_PARAVIRT_GUEST=|CONFIG_PARAVIRT_SPINLOCKS=|CONFIG_XEN=|CONFIG_
>>> On 01.02.16 at 13:02, wrote:
> On Mon, Feb 01, 2016 at 12:52:51AM -0700, Jan Beulich wrote:
>> >>> On 30.01.16 at 15:38, wrote:
>>
>> > On 1/30/2016 12:33 AM, Jan Beulich wrote:
>> > On 29.01.16 at 11:45, wrote:
>> >>> --- a/xen/arch/x86/hvm/hvm.c
>> >>> +++ b/xen/arch/x86/hvm/hvm.c
>>
>>> On 01.02.16 at 13:01, wrote:
> On 01/02/16 11:58, Jan Beulich wrote:
>> Commit 599bad38cf added BUS_NOTIFY_REMOVED_DEVICE in order to allow
>> avoiding removal of IOMMU mappings before the driver actually got
>> unbound from the device. Naturally we should be using this too.
>
> Because other
On Mon, Feb 01, 2016 at 05:11:19AM -0700, Jan Beulich wrote:
> >>> On 01.02.16 at 11:45, wrote:
> > * xsave/xrtors support
> > - Shuai Ruan
>
> As per
> http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg03264.html
> and even more importantly
> http://lists.xenproject.org/archives
>>> On 29.01.16 at 20:17, wrote:
> c/s 0f1cb96e "x86 hvm: Allow cross-vendor migration" caused HVM domains to
> unconditionally intercept #UD exceptions. While cross-vendor migration is
> cool as a demo, it is extremely niche.
>
> Intercepting #UD allows userspace code in a multi-vcpu guest to e
flight 79603 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79603/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail
REGR. vs. 65543
test-amd64-i386-
On 02/01/2016 01:59 AM, Wei Liu wrote:
(Cc Roger)
On Sun, Jan 31, 2016 at 01:27:23PM -0800, PGNet Dev wrote:
I run Xen 4.6 Dom0
rpm -qa | egrep -i "kernel-default-4|xen-4"
kernel-default-devel-4.4.0-8.1.g9f68b90.x86_64
xen-4.6.0_08-405.1.x86_64
My guest
On Mon, Feb 01, 2016 at 04:23:46AM -0800, PGNet Dev wrote:
> On 02/01/2016 01:59 AM, Wei Liu wrote:
> >(Cc Roger)
> >
> >On Sun, Jan 31, 2016 at 01:27:23PM -0800, PGNet Dev wrote:
> >>I run Xen 4.6 Dom0
> >>
> >>rpm -qa | egrep -i "kernel-default-4|xen-4"
> >>kernel-default-devel-4.
On Mon, Feb 01, 2016 at 12:59:00AM -0700, Jan Beulich wrote:
> >>> On 30.01.16 at 02:47, wrote:
> > On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
> >> (re-adding xen-devel)
> >>
> >> >>> On 26.01.16 at 12:28, wrote:
> >> > Iommu=0 let the whole Qubes system work, without enforcing
El 01/02/16 a les 13.23, PGNet Dev ha escrit:
> On 02/01/2016 01:59 AM, Wei Liu wrote:
>
> (1) http://xenbits.xen.org/docs/unstable/misc/pvh.html
>
> which also looks 'dusty'
>
> This looks more promising,
>
> (2) https://github.com/mirage/xen/blob/master/docs/misc/pvh.markdown
>
> That the on
On 02/01/2016 02:28 AM, Roger Pau Monné wrote:
Do any of these^^ params need to also change with the addition of
pvh = 1
Yes, you need to remove builder, xen_platform_pci and
device_model_version, and add a kernel and ramdisk parameters that point
to the actual kernel and ramdisk tha
>>> On 01.02.16 at 13:28, wrote:
> On Mon, Feb 01, 2016 at 12:59:00AM -0700, Jan Beulich wrote:
>> >>> On 30.01.16 at 02:47, wrote:
>> > On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
>> >> (re-adding xen-devel)
>> >>
>> >> >>> On 26.01.16 at 12:28, wrote:
>> >> > Iommu=0 let the
On 02/01/2016 04:29 AM, Roger Pau Monné wrote:
http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=docs/misc/pvh.markdown
That's all sorted now, thanks.
I'll get the dom0pvh issue logs posted.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://
flight 79602 linux-3.10 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79602/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 78980
build-amd64-rumpuserxe
Hi,
> Thanks for the tip that seabios allocated pages automatically become
> e820 reserved, that simplifies things a bit.
It's common practice for all firmware. The e820 table from qemu is just
a starting point, it is not passed on to the guest os as-is. All
permanent allocations (acpi tables
On Mon, Feb 01, 2016 at 05:15:16AM -0700, Jan Beulich wrote:
> >>> On 01.02.16 at 13:02, wrote:
> > On Mon, Feb 01, 2016 at 12:52:51AM -0700, Jan Beulich wrote:
> >> >>> On 30.01.16 at 15:38, wrote:
> >>
> >> > On 1/30/2016 12:33 AM, Jan Beulich wrote:
> >> > On 29.01.16 at 11:45, wrote:
>
flight 79587 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79587/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 59254
build-amd64-rumpuserx
On 01/02/16 12:16, Jan Beulich wrote:
On 01.02.16 at 13:01, wrote:
>> On 01/02/16 11:58, Jan Beulich wrote:
>>> Commit 599bad38cf added BUS_NOTIFY_REMOVED_DEVICE in order to allow
>>> avoiding removal of IOMMU mappings before the driver actually got
>>> unbound from the device. Naturally we s
>>> On 01.02.16 at 13:49, wrote:
> On Mon, Feb 01, 2016 at 05:15:16AM -0700, Jan Beulich wrote:
>> >>> On 01.02.16 at 13:02, wrote:
>> > On Mon, Feb 01, 2016 at 12:52:51AM -0700, Jan Beulich wrote:
>> >> >>> On 30.01.16 at 15:38, wrote:
>> >>
>> >> > On 1/30/2016 12:33 AM, Jan Beulich wrote:
>>
>>> On 01.02.16 at 14:03, wrote:
> On 01/02/16 12:16, Jan Beulich wrote:
> On 01.02.16 at 13:01, wrote:
>>> On 01/02/16 11:58, Jan Beulich wrote:
Commit 599bad38cf added BUS_NOTIFY_REMOVED_DEVICE in order to allow
avoiding removal of IOMMU mappings before the driver actually got
>>>
On Mon, Feb 01, 2016 at 11:22:03AM +, David Woodhouse wrote:
> On Thu, 2016-01-28 at 18:31 -0800, Andy Lutomirski wrote:
> > This is a kludge, but no one has come up with a a better idea yet.
> > We'll introduce DMA API support guarded by vring_use_dma_api().
> > Eventually we may be able to re
Ping? (I'd really like to get this resolved, so we don't need to
indefinitely run with non-upstream behavior in our distros.)
Thanks, Jan
>>> On 13.01.16 at 17:15, wrote:
On 13.01.16 at 17:00, wrote:
>> On 13/01/16 15:36, Jan Beulich wrote:
>> On 13.01.16 at 16:25, wrote:
On 12/0
I'll get the dom0pvh issue logs posted.
http://xenbits.xen.org/docs/unstable/misc/pvh-readme.txt
" ...
To boot 64bit dom0 in PVH mode, add dom0pvh to grub xen command line.
..."
http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=docs/misc/pvh.markdown
no mention
On 01/02/16 13:20, Jan Beulich wrote:
> Ping? (I'd really like to get this resolved, so we don't need to
> indefinitely run with non-upstream behavior in our distros.)
>
> Thanks, Jan
My remaining issue is whether this loop gets executed by default.
I realise that there is a difference between le
On 02/01/2016 05:28 AM, Roger Pau Monné wrote:
IIRC Boris (CCed) added support for 32bit PVH to Linux, so you should
be able to use either 32 or 64 kernels. Roger.
This actually never happened for Linux: HVMlite showed up fast enough
that it didn't make sense anymore to add 32-bit support to
Wei Liu writes ("Re: [PATCH 3/4] libxl/remus: Change the assert for info to an
return"):
> On Tue, Jan 26, 2016 at 04:30:59PM -0500, Konrad Rzeszutek Wilk wrote:
> > The assert(info) is after quite a lot of manipulations
> > on 'info' - which makes the assert pointless because if
> > info was NULL
1 - 100 of 233 matches
Mail list logo
