On Wed, 2014-12-03 at 15:36 -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Dec 03, 2014 at 04:53:53PM +0100, Daniel Kiper wrote:
> > On Tue, Dec 02, 2014 at 01:36:20PM -0500, Konrad Rzeszutek Wilk wrote:
> > > On Tue, Dec 02, 2014 at 04:16:28PM +0100, Daniel Kiper wrote:
> > > > Signed-off-by: Danie
>>> On 03.12.14 at 16:37, wrote:
> On Tue, Dec 02, 2014 at 03:58:53PM +, Jan Beulich wrote:
>> >>> Daniel Kiper 12/02/14 3:58 PM >>>
>> >In general initial conring size is sufficient. However, if log
>> >level is increased on platforms which have e.g. huge number
>> >of memory regions (I have
flight 32044 xen-4.3-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/32044/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 31811
Tests which are f
>>> On 03.12.14 at 21:13, wrote:
> On 11/27/2014 03:57 AM, Jan Beulich wrote:
> On 26.11.14 at 15:32, wrote:
>>> On 11/25/2014 08:49 AM, Jan Beulich wrote:
>>> On 17.11.14 at 00:07, wrote:
> @@ -244,19 +256,19 @@ void vpmu_initialise(struct vcpu *v)
>switch ( vendor )
>>>
On 12/2/2014 7:40 PM, Tim Deegan wrote:
At 15:38 +0800 on 02 Dec (1417531126), Yu, Zhang wrote:
On 12/1/2014 8:13 PM, Tim Deegan wrote:
At 11:17 + on 01 Dec (1417429027), Jan Beulich wrote:
On 01.12.14 at 11:30, wrote:
During this bit of archaeology I realised that either this new type
On Wed, 2014-12-03 at 21:31 -0400, Konrad Rzeszutek Wilk wrote:
> so something is busted as you surmised
I haven't been following closely, so this may be completely unrelated to
the issue under discussion, but doesn't in-HVM-guest hotplug require a
guest side driver to be loaded? I recall in the d
>>> On 03.12.14 at 22:02, wrote:
> Hey,
>
> 1) Why is there in EFI code so many functions (e.g. efi_start(),
>efi_arch_edd(), ...) with local variables declared as a static?
>Though some of them have also regular local variables. I do not
>why it was decided that some of them must be
Hi,
At 17:01 +0800 on 04 Dec (1417708878), Yu, Zhang wrote:
> I just noticed that in __hvm_copy()/__hvm_clear(), the grant types are
> handled before the p2m_ram_ro - will return HVMCOPY_unhandleable. So if
> p2m_is_discard_write() is supposed to replace the handling of
> p2m_ram_ro, handling o
HI,
Looking at the function __xenbus_switch_state in file
source/drivers/xen/xenbus/xenbus_client.c,
The comment says:
"We check whether the state is currently set to the given value, and
if not, then the state is set."
The code loads the old state value, but never does anything wit
On 12/4/2014 5:36 PM, Tim Deegan wrote:
Hi,
At 17:01 +0800 on 04 Dec (1417708878), Yu, Zhang wrote:
I just noticed that in __hvm_copy()/__hvm_clear(), the grant types are
handled before the p2m_ram_ro - will return HVMCOPY_unhandleable. So if
p2m_is_discard_write() is supposed to replace the
flight 32051 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/32051/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-pvops 5 kernel-build fail REGR. vs. 31986
Regressions which ar
Hi,
I am new to the world of *"Xen on ARM"* would like to seek help from
community on how can I install Xen on ARM on a Nexus Phone / Tablet or an
emulator
I actually wish to try and install a unikernel : LING (Erlang on Xen) on
top of the hypervisor dual booted with Android or QNX on a mobile ph
Il 04/12/2014 03:45, Jike Song ha scritto:
Hi all,
We're pleased to announce a public release to Intel Graphics
Virtualization Technology (Intel GVT-g, formerly known as XenGT).
Intel GVT-g is a complete vGPU solution with mediated pass-through,
supported today on 4th generation Intel Core(TM
On 04/12/14 00:50, Julien Grall wrote:
> Hi Vitaly,
>
> On 03/12/2014 17:16, Vitaly Kuznetsov wrote:
>> New operation sets the 'recipient' domain which will recieve all
>
> s/recieve/receive/
>
>> memory pages from a particular domain and kills the original domain.
>>
>> Signed-off-by: Vitaly Ku
On 04/12/14 01:50, Zhang, Yang Z wrote:
> Konrad Rzeszutek Wilk wrote on 2014-12-03:
>> On Wed, Dec 03, 2014 at 09:38:49AM +, Ian Campbell wrote:
>>> On Tue, 2014-12-02 at 16:09 -0500, Konrad Rzeszutek Wilk wrote:
On Fri, Nov 28, 2014 at 11:50:43AM +, Ian Campbell wrote:
> On Fri,
On 04/12/14 09:40, Andrew Reimers wrote:
> HI,
>
> Looking at the function __xenbus_switch_state in file
> source/drivers/xen/xenbus/xenbus_client.c,
>
> The comment says:
>
> "We check whether the state is currently set to the given value, and
> if not, then the state is set."
>
> Th
On 03/12/14 20:38, Konrad Rzeszutek Wilk wrote:
> On Wed, Dec 03, 2014 at 04:04:20PM +, David Vrabel wrote:
>> The default limit for the number of PIRQs for hardware domains (dom0)
>> is not sufficient for some (x86) systems.
>>
>> Since the pirq structures are individually and dynamically allo
> From: Fabio Fantoni [mailto:fabio.fant...@m2r.biz]
> Sent: Thursday, December 04, 2014 6:20 PM
>
> Il 04/12/2014 03:45, Jike Song ha scritto:
> > Hi all,
> >
> > We're pleased to announce a public release to Intel Graphics
> > Virtualization Technology (Intel GVT-g, formerly known as XenGT).
> >
On Thu, 2014-12-04 at 15:44 +0530, Sagun Garg wrote:
> Hi,
>
>
> I am new to the world of "Xen on ARM" would like to seek help from
> community on how can I install Xen on ARM on a Nexus Phone / Tablet or
> an emulator
>
>
> I actually wish to try and install a unikernel : LING (Erlang on Xen)
On 03/12/14 18:42, Andrew Cooper wrote:
>
> XSA-37 was only an XSA because the rules at the time were unclear as
> whether it was an issue or not. At the same time, the rules were
> clarified to state that issues in a debug build only are not security
> issues.
Given that we occasionally ask our
On Wed, Dec 03, 2014 at 02:43:37PM +, Zhangleiqiang (Trump) wrote:
> > -Original Message-
> > From: Wei Liu [mailto:wei.l...@citrix.com]
> > Sent: Tuesday, December 02, 2014 11:59 PM
> > To: Zhangleiqiang (Trump)
> > Cc: Wei Liu; zhangleiqiang; xen-devel@lists.xen.org; Luohao (brian);
On 04/12/2014 10:19, David Vrabel wrote:
On 04/12/14 00:50, Julien Grall wrote:
Hi Vitaly,
On 03/12/2014 17:16, Vitaly Kuznetsov wrote:
New operation sets the 'recipient' domain which will recieve all
s/recieve/receive/
memory pages from a particular domain and kills the original domain.
On 02/12/14 20:19, Boris Ostrovsky wrote:
> Changes in v4:
> * Added comment describing what we check for in pci_xen_init()
I applied v3 ages ago to the devel/for-linus-3.19 branch and I'm not
going to mess about replacing it for a comment change.
David
__
On 03/12/2014 17:16, Vitaly Kuznetsov wrote:
diff --git a/xen/include/xen/sched.h b/xen/include/xen/sched.h
index a42d0b8..552e4a3 100644
--- a/xen/include/xen/sched.h
+++ b/xen/include/xen/sched.h
@@ -366,6 +366,8 @@ struct domain
bool_t is_privileged;
/* Which guest this
On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote:
> From: Jan Beulich
>
> When a PF driver unloads, it may find it necessary to leave the VFs
> around simply because of pciback having marked them as assigned to a
> guest. Utilize a suitable notification to let go of the VFs, thus
> allowing the PF
On 12/04/2014 10:37 AM, David Vrabel wrote:
> On 03/12/14 18:42, Andrew Cooper wrote:
>>
>> XSA-37 was only an XSA because the rules at the time were unclear as
>> whether it was an issue or not. At the same time, the rules were
>> clarified to state that issues in a debug build only are not secur
On Wed, Dec 03, Vitaly Kuznetsov wrote:
> Original description:
>
> When a PVHVM linux guest performs kexec there are lots of things which
> require taking care of:
> - shared info, vcpu_info
> - grants
> - event channels
> - ...
> Instead of taking care of all these things we can rebuild the dom
On Tue, Dec 02, 2014 at 04:34:08PM -0500, Boris Ostrovsky wrote:
[...]
> void libxl_cputopology_list_free(libxl_cputopology *, int nb_cpu);
>
> +#define LIBXL_TOPOLOGY_INVALID_ENTRY (~(uint32_t)0)
> +libxl_topology *libxl_get_topology(libxl_ctx *ctx);
> +void libxl_topology_free(libxl_topology *
On 04/12/14 11:12, George Dunlap wrote:
> On 12/04/2014 10:37 AM, David Vrabel wrote:
>> On 03/12/14 18:42, Andrew Cooper wrote:
>>>
>>> XSA-37 was only an XSA because the rules at the time were unclear as
>>> whether it was an issue or not. At the same time, the rules were
>>> clarified to state
On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote:
>
> Instead of doing all this complex dance, we depend on the toolstack
> doing the right thing. As such implement the 'do_flr' SysFS attribute
> which 'xl' uses when a device is detached or attached from/to a guest.
> It bypasses the need to worry a
>>> On 04.12.14 at 12:07, wrote:
> On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote:
>> From: Jan Beulich
>>
>> When a PF driver unloads, it may find it necessary to leave the VFs
>> around simply because of pciback having marked them as assigned to a
>> guest. Utilize a suitable notification to l
On Wed, Dec 03, 2014 at 06:16:12PM +0100, Vitaly Kuznetsov wrote:
> Changes from RFCv3:
> This is the first non-RFC series as no major concerns were expressed. I'm
> trying
> to address Jan's comments. Changes are:
> - Move from XEN_DOMCTL_set_recipient to XEN_DOMCTL_devour (I don't really like
>
On Wed, 2014-12-03 at 10:51 +, Ian Campbell wrote:
> On Wed, 2014-12-03 at 11:49 +0100, Olaf Hering wrote:
> > On Wed, Dec 03, Ian Campbell wrote:
> >
> > > Ah I didn't know about the sd_listen_fds thing, so I think that what we
> > > need then is to use pkg-config first to determine if system
On Tue, 2014-12-02 at 16:34 -0500, Boris Ostrovsky wrote:
> Make XEN_SYSCTL_topologyinfo more generic so that it can return both
> CPU and IO topology (support for returning the latter is added in the
> subsequent patch)
>
Is it always the case that we need the full information (i.e., both CPU
and
On Dec 4, 2014 4:29 AM, "Ian Campbell" wrote:
>
> On Wed, 2014-12-03 at 21:31 -0400, Konrad Rzeszutek Wilk wrote:
> > so something is busted as you surmised
>
> I haven't been following closely, so this may be completely unrelated to
> the issue under discussion, but doesn't in-HVM-guest hotplug r
On Dec 4, 2014 6:30 AM, David Vrabel wrote:
>
> On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote:
> >
> > Instead of doing all this complex dance, we depend on the toolstack
> > doing the right thing. As such implement the 'do_flr' SysFS attribute
> > which 'xl' uses when a device is detached o
> -Original Message-
> From: Wei Liu [mailto:wei.l...@citrix.com]
> Sent: Thursday, December 04, 2014 6:50 PM
> To: Zhangleiqiang (Trump)
> Cc: Wei Liu; xen-devel@lists.xen.org; zhangleiqiang; Luohao (brian); Xiaoding
> (B); Yuzhou (C); Zhuangyuxin
> Subject: Re: [Xen-devel] Poor network pe
On Dec 4, 2014 6:55 AM, Ian Campbell wrote:
>
> On Wed, 2014-12-03 at 10:51 +, Ian Campbell wrote:
> > On Wed, 2014-12-03 at 11:49 +0100, Olaf Hering wrote:
> > > On Wed, Dec 03, Ian Campbell wrote:
> > >
> > > > Ah I didn't know about the sd_listen_fds thing, so I think that what we
> >
On Wed, 3 Dec 2014, Konrad Rzeszutek Wilk wrote:
> On Wed, Dec 03, 2014 at 06:20:41PM +, Stefano Stabellini wrote:
> > If the new target is relative to the current target, do not remove
> > videoram again: it has already been removed from the current target.
>
> Please explain:
> - Is this an
flight 32055 xen-4.4-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/32055/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 31781
Tests which are f
On Tue, 2014-12-02 at 16:34 -0500, Boris Ostrovsky wrote:
> --- a/tools/libxl/libxl_internal.h
> +++ b/tools/libxl/libxl_internal.h
> @@ -1168,6 +1168,11 @@ _hidden int libxl__try_phy_backend(mode_t st_mode);
>
> _hidden char *libxl__devid_to_localdev(libxl__gc *gc, int devid);
>
> +_hidden i
On 04/12/14 12:06, Konrad Rzeszutek Wilk wrote:
>
> On Dec 4, 2014 6:30 AM, David Vrabel wrote:
>>
>> On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote:
>>>
>>> Instead of doing all this complex dance, we depend on the toolstack
>>> doing the right thing. As such implement the 'do_flr' SysFS attri
On Wed, 3 Dec 2014, Don Slutz wrote:
> On 12/03/14 13:20, Stefano Stabellini wrote:
> > If the new target is relative to the current target, do not remove
> > videoram again: it has already been removed from the current target.
> >
> > Signed-off-by: Stefano Stabellini
> >
> > diff --git a/tools
Currently, Xens stack tracing and dumping of its own stacks will always
attempt to continue to the top of the primary stack. While this is fine for
99% of cases, it is incorrect when the stack pointer starts on an IST stack.
In particular, the stack analysis functions will wander up from the IST
On Wed, 2014-12-03 at 10:57 -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Dec 03, 2014 at 09:52:34AM +0100, Olaf Hering wrote:
> > Signed-off-by: Olaf Hering
> > Cc: Ian Campbell
> > Cc: Ian Jackson
> > ---
> > INSTALL | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> This being a
On Wed, 2014-12-03 at 11:20 -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Dec 03, 2014 at 10:50:34AM +, Ian Campbell wrote:
> > On Wed, 2014-12-03 at 10:41 +, Wei Liu wrote:
> > > In e3abab74 (libxl: un-constify return value of libxl_basename), the
> > > macro was exposed to releases < 4.5.
On Thu, Dec 04, 2014 at 12:09:33PM +, Zhangleiqiang (Trump) wrote:
[...]
> > > However, I find another issue. Even using 6 queues and making sure
> > > that all of these 6 netback processes running with high cpu usage
> > > (indeed, any of it running with 87% cpu usage), the whole VM receive
>
Thursday, December 4, 2014, 1:24:47 PM, you wrote:
> On 04/12/14 12:06, Konrad Rzeszutek Wilk wrote:
>>
>> On Dec 4, 2014 6:30 AM, David Vrabel wrote:
>>>
>>> On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote:
Instead of doing all this complex dance, we depend on the toolstack
doi
On Tue, 2014-12-02 at 16:16 +0100, Daniel Kiper wrote:
> Signed-off-by: Daniel Kiper
.gitignore updates seem harmless enough. so I've applied this and the
third patch. Awaiting Konrad's verdict on the first.
> ---
> .gitignore |3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/.git
On Tue, 2014-12-02 at 15:42 -0500, Konrad Rzeszutek Wilk wrote:
> On Tue, Dec 02, 2014 at 06:51:50PM +, M A Young wrote:
> > On Tue, 2 Dec 2014, Konrad Rzeszutek Wilk wrote:
> >
> > >On Tue, Dec 02, 2014 at 03:44:55PM +, Ian Campbell wrote:
> > >>On Tue, 2014-12-02 at 16:39 +0100, Olaf Her
On Tue, 2014-12-02 at 13:47 -0500, Konrad Rzeszutek Wilk wrote:
> On Tue, Dec 02, 2014 at 01:50:37PM +, Ian Campbell wrote:
> > On Mon, 2014-12-01 at 16:14 -0500, Konrad Rzeszutek Wilk wrote:
> > > On Fri, Nov 28, 2014 at 11:38:52AM +, Ian Campbell wrote:
> > > > On Thu, 2014-11-27 at 12:34
On Tue, 2014-12-02 at 10:09 -0500, Konrad Rzeszutek Wilk wrote:
> > At this point in a freeze I'm much happier with:
> >
> > tools/pygrub/src/pygrub |4 +++-
> > 1 files changed, 3 insertions(+), 1 deletions(-)
>
> The same here. This is now the season of handing out band-aids.
>
> As such
On Tue, 2014-12-02 at 14:36 +, Ian Campbell wrote:
> > When executed, the softirq will notice that the timer has to be fired
> > and therefore an interrupt will be injected to the guest.
>
> Perfect, thanks.
Konrad RM-acked it, so I have committed with the tweaks I mentioned.
On Tue, 2014-12-02 at 13:43 -0500, Konrad Rzeszutek Wilk wrote:
> On Tue, Dec 02, 2014 at 04:04:44PM +, Wei Liu wrote:
> > On Tue, Dec 02, 2014 at 04:18:08PM +0100, Vitaly Kuznetsov wrote:
> > > XEN_DOMCTL_getdomaininfo, which is being used by xc_domain_getinfo(), has
> > > strange interface: i
On Thu, 2014-12-04 at 07:13 -0500, Konrad Rzeszutek Wilk wrote:
> On Dec 4, 2014 6:55 AM, Ian Campbell wrote:
> >
> > On Wed, 2014-12-03 at 10:51 +, Ian Campbell wrote:
> > > On Wed, 2014-12-03 at 11:49 +0100, Olaf Hering wrote:
> > > > On Wed, Dec 03, Ian Campbell wrote:
> > > >
> > > > >
On Thu, 2014-12-04 at 13:22 +0100, Dario Faggioli wrote:
> On Tue, 2014-12-02 at 16:34 -0500, Boris Ostrovsky wrote:
>
> > --- a/tools/libxl/libxl_internal.h
> > +++ b/tools/libxl/libxl_internal.h
> > @@ -1168,6 +1168,11 @@ _hidden int libxl__try_phy_backend(mode_t st_mode);
> >
> > _hidden cha
>>> On 04.12.14 at 13:58, wrote:
> Konrad: I am requesting a release ack for this change. It aids the clarity of
> certain crash information, and prevents cascade pagefaults in certain
> circumstances, which would prevent execution of the crash kernel or a system
> reboot.
With
#ifndef NDEBUG
#
On 04/12/14 12:09, Zhangleiqiang (Trump) wrote:
I think that's expected, because guest RX data path still uses grant_copy while
>guest TX uses grant_map to do zero-copy transmit.
As I understand, the RX process is as follows:
1. Phy NIC receive packet
2. XEN Hypervisor trigger interrupt to Dom
On 04/12/14 13:10, Sander Eikelenboom wrote:
>
> Thursday, December 4, 2014, 1:24:47 PM, you wrote:
>
>> On 04/12/14 12:06, Konrad Rzeszutek Wilk wrote:
>>>
>>> On Dec 4, 2014 6:30 AM, David Vrabel wrote:
On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote:
>
> Instead of doing all
XenGT (Intel Graphics Virtualization technology, please refer to
https://01.org/xen/blogs/srclarkx/2013/graphics-virtualization-
xengt) driver runs inside Dom0 as a virtual graphics device model,
and needs to trap and emulate the guest's write operations to some
specific memory pages, like memory p
From: Yu Zhang
Currently, the P2M_RO_TYPES bears 2 meanings: one is
"_PAGE_RW bit is clear in their PTEs", and another is
to discard the write operations on these pages. This
patch adds a p2m type class, P2M_DISCARD_WRITE_TYPES,
to bear the second meaning, so we can use this type
class instead of
From: Yu Zhang
A new p2m type, p2m_mmio_write_dm, is added to trap and emulate
the write operations on GPU's page tables. Handling of this new
p2m type are similar with existing p2m_ram_ro in most condition
checks, with only difference on final policy of emulation vs. drop.
For p2m_ram_ro types,
On 04/12/14 10:56, David Vrabel wrote:
> On 02/12/14 20:19, Boris Ostrovsky wrote:
>> Changes in v4:
>> * Added comment describing what we check for in pci_xen_init()
>
> I applied v3 ages ago to the devel/for-linus-3.19 branch and I'm not
> going to mess about replacing it for a comment change.
>>> On 28.11.14 at 16:46, wrote:
> On 28/11/14 15:18, Jan Beulich wrote:
> On 28.11.14 at 14:55, wrote:
>>> The problem is with continuations which reuse the upper bits of the
>>> input register, not with this HVMOP_op_mask specifically; the
>>> HVMOP_op_mask simply adds to an existing proble
On 04/12/14 03:50, Vijay Kilari wrote:
> Hi Tim,
Hi Vijay,
> I see that on uart interrupt, ICR is written to clear the all
> interrupts except TX, RX and RX timeout. With this, cpu always finds
> TX/RX is active and never
> comes out of the loop.
FWIW, the PL011 serial code has been copied from
Hi,
following is a patch against vanilla Mini-OS in upstream xen.git for a
problem we have found in the netfront driver. When subjected to load
network receive would freeze due to the rx ring running out of free
request slots.
With this patch a httpd running on rumprun-xen [1] survives all the lo
Thursday, December 4, 2014, 2:43:06 PM, you wrote:
> On 04/12/14 13:10, Sander Eikelenboom wrote:
>>
>> Thursday, December 4, 2014, 1:24:47 PM, you wrote:
>>
>>> On 04/12/14 12:06, Konrad Rzeszutek Wilk wrote:
On Dec 4, 2014 6:30 AM, David Vrabel wrote:
>
> On 03/12/14 21:40,
Hello Sander,
Thursday, December 4, 2014, 3:09:09 PM, you wrote:
> Thursday, December 4, 2014, 2:43:06 PM, you wrote:
>> On 04/12/14 13:10, Sander Eikelenboom wrote:
>>>
>>> Thursday, December 4, 2014, 1:24:47 PM, you wrote:
>>>
On 04/12/14 12:06, Konrad Rzeszutek Wilk wrote:
>
>
On 04/12/14 13:32, Jan Beulich wrote:
On 04.12.14 at 13:58, wrote:
>> Konrad: I am requesting a release ack for this change. It aids the clarity
>> of
>> certain crash information, and prevents cascade pagefaults in certain
>> circumstances, which would prevent execution of the crash kernel
Hi,
In rumprun-xen [1] we use Mini-OS as a "base firmware" layer in our stack.
Currently we are using a slightly bastardized fork of the xen.git Mini-OS.
We would like to avoid this turning into a permanent fork. Following
previous discussion [2] on and openmirage-devel I would like to coordinate
On 04/12/14 13:49, Jan Beulich wrote:
On 28.11.14 at 16:46, wrote:
>> On 28/11/14 15:18, Jan Beulich wrote:
>> On 28.11.14 at 14:55, wrote:
The problem is with continuations which reuse the upper bits of the
input register, not with this HVMOP_op_mask specifically; the
HVM
Olaf Hering writes:
> On Wed, Dec 03, Vitaly Kuznetsov wrote:
>
>> Original description:
>>
>> When a PVHVM linux guest performs kexec there are lots of things which
>> require taking care of:
>> - shared info, vcpu_info
>> - grants
>> - event channels
>> - ...
>> Instead of taking care of all t
On 04/12/14 14:09, Sander Eikelenboom wrote:
>
> Thursday, December 4, 2014, 2:43:06 PM, you wrote:
>
>> On 04/12/14 13:10, Sander Eikelenboom wrote:
>>>
>>> Thursday, December 4, 2014, 1:24:47 PM, you wrote:
>>>
On 04/12/14 12:06, Konrad Rzeszutek Wilk wrote:
>
> On Dec 4, 2014 6:30
> -Original Message-
> From: Zoltan Kiss [mailto:zoltan.k...@linaro.org]
> Sent: Thursday, December 04, 2014 9:35 PM
> To: Zhangleiqiang (Trump); Wei Liu; xen-devel@lists.xen.org
> Cc: Xiaoding (B); Zhuangyuxin; zhangleiqiang; Luohao (brian); Yuzhou (C)
> Subject: Re: [Xen-devel] Poor netwo
Thanks for your detailed explanation, Wei.
I am wondering if netfront/netback can be optimized to reach the 10Gbps
throughout between DomUs running on different hosts connected with 10GE
network. Currently, it seems like the RX is the bottleneck, which also consist
with the testing result in x
On 04/12/14 14:27, Martin Lucina wrote:
> Hi,
>
> In rumprun-xen [1] we use Mini-OS as a "base firmware" layer in our stack.
> Currently we are using a slightly bastardized fork of the xen.git Mini-OS.
>
> We would like to avoid this turning into a permanent fork. Following
> previous discussion [2
Wei Liu writes:
> On Wed, Dec 03, 2014 at 06:16:12PM +0100, Vitaly Kuznetsov wrote:
>> Changes from RFCv3:
>> This is the first non-RFC series as no major concerns were expressed. I'm
>> trying
>> to address Jan's comments. Changes are:
>> - Move from XEN_DOMCTL_set_recipient to XEN_DOMCTL_devou
Julien Grall writes:
> On 03/12/2014 17:16, Vitaly Kuznetsov wrote:
>> diff --git a/xen/include/xen/sched.h b/xen/include/xen/sched.h
>> index a42d0b8..552e4a3 100644
>> --- a/xen/include/xen/sched.h
>> +++ b/xen/include/xen/sched.h
>> @@ -366,6 +366,8 @@ struct domain
>> bool_t i
Thursday, December 4, 2014, 3:31:11 PM, you wrote:
> On 04/12/14 14:09, Sander Eikelenboom wrote:
>>
>> Thursday, December 4, 2014, 2:43:06 PM, you wrote:
>>
>>> On 04/12/14 13:10, Sander Eikelenboom wrote:
Thursday, December 4, 2014, 1:24:47 PM, you wrote:
> On 04/12/14 12:0
>>> On 04.12.14 at 15:28, wrote:
> On 04/12/14 13:49, Jan Beulich wrote:
> On 28.11.14 at 16:46, wrote:
>>> On 28/11/14 15:18, Jan Beulich wrote:
>>> On 28.11.14 at 14:55, wrote:
> The problem is with continuations which reuse the upper bits of the
> input register, not with this
On Thu, Dec 04, 2014 at 03:46:59PM +0100, Vitaly Kuznetsov wrote:
> Wei Liu writes:
>
> > On Wed, Dec 03, 2014 at 06:16:12PM +0100, Vitaly Kuznetsov wrote:
> >> Changes from RFCv3:
> >> This is the first non-RFC series as no major concerns were expressed. I'm
> >> trying
> >> to address Jan's co
Julien Grall writes:
> Hi Vitaly,
>
> On 03/12/2014 17:16, Vitaly Kuznetsov wrote:
>> New operation sets the 'recipient' domain which will recieve all
>
> s/recieve/receive/
>
>> memory pages from a particular domain and kills the original domain.
>>
>> Signed-off-by: Vitaly Kuznetsov
>> ---
>>
>>> On 01.12.14 at 10:24, wrote:
> --- a/xen/drivers/passthrough/pci.c
> +++ b/xen/drivers/passthrough/pci.c
> @@ -34,6 +34,7 @@
> #include
> #include
> #include
> +#include
Please don't - we use bool_t in the hypervisor, not bool. The header
only exists for source code shared with the too
> On 01/12/14 14:22, David Vrabel wrote:
> This VIF protocol is weird. The first slot contains a txreq with a
> size
> for the total length of the packet, subsequent slots have sizes for
> that
> fragment only.
>
> netback then has to calculate how long the first slot is, by
> subtracting
> all th
On Thu, 2014-12-04 at 15:50 +0100, Sander Eikelenboom wrote:
> Thursday, December 4, 2014, 3:31:11 PM, you wrote:
>
> > On 04/12/14 14:09, Sander Eikelenboom wrote:
> >>
> >> Thursday, December 4, 2014, 2:43:06 PM, you wrote:
> >>
> >>> On 04/12/14 13:10, Sander Eikelenboom wrote:
>
>
At 13:51 + on 04 Dec (1417697518), Julien Grall wrote:
> On 04/12/14 03:50, Vijay Kilari wrote:
> > Hi Tim,
>
> Hi Vijay,
>
> > I see that on uart interrupt, ICR is written to clear the all
> > interrupts except TX, RX and RX timeout. With this, cpu always finds
> > TX/RX is active and never
On 28/11/14 10:53, Juergen Gross wrote:
> Paravirtualized kernels running on Xen use a three level tree for
> translation of guest specific physical addresses to machine global
> addresses. This p2m tree is used for construction of page table
> entries, so the p2m tree walk is performance critical.
On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote:
>
> These patches fix some issues with PCI back and also add proper
> bus/slot reset.
Applied 1-8 to devel/for-linus-3.19. I did not apply #9.
Thanks.
David
___
Xen-devel mailing list
Xen-devel@lists.x
On 04/12/14 14:55, Jan Beulich wrote:
On 04.12.14 at 15:28, wrote:
>> On 04/12/14 13:49, Jan Beulich wrote:
>> On 28.11.14 at 16:46, wrote:
On 28/11/14 15:18, Jan Beulich wrote:
On 28.11.14 at 14:55, wrote:
>> The problem is with continuations which reuse the upper bit
At 14:28 + on 04 Dec (1417699730), Andrew Cooper wrote:
> On 04/12/14 13:49, Jan Beulich wrote:
> On 28.11.14 at 16:46, wrote:
> >> On 28/11/14 15:18, Jan Beulich wrote:
> >> On 28.11.14 at 14:55, wrote:
> The problem is with continuations which reuse the upper bits of the
> >>>
>>> On 01.12.14 at 10:24, wrote:
> We need to use reserved device memory maps with multiple times, so
> provide just one common function should be friend.
I'm not going to repeat earlier comments; the way this is done right
now it's neither a proper runtime function nor a proper init time one.
J
On 12/04/2014 03:51 AM, Jan Beulich wrote:
On 03.12.14 at 21:13, wrote:
On 11/27/2014 03:57 AM, Jan Beulich wrote:
On 26.11.14 at 15:32, wrote:
On 11/25/2014 08:49 AM, Jan Beulich wrote:
On 17.11.14 at 00:07, wrote:
@@ -244,19 +256,19 @@ void vpmu_initialise(struct vcpu *v)
switch
On 04/12/14 15:36, Anthony Wright wrote:
>> On 01/12/14 14:22, David Vrabel wrote:
>> This VIF protocol is weird. The first slot contains a txreq with a
>> size
>> for the total length of the packet, subsequent slots have sizes for
>> that
>> fragment only.
>>
>> netback then has to calculate how l
On 04/12/14 15:12, Vitaly Kuznetsov wrote:
> Julien Grall writes:
>
>> Hi Vitaly,
>>
>> On 03/12/2014 17:16, Vitaly Kuznetsov wrote:
>>> New operation sets the 'recipient' domain which will recieve all
>>
>> s/recieve/receive/
>>
>>> memory pages from a particular domain and kills the original do
At 21:13 +0800 on 04 Dec (1417724005), Yu Zhang wrote:
> From: Yu Zhang
>
> Currently, the P2M_RO_TYPES bears 2 meanings: one is
> "_PAGE_RW bit is clear in their PTEs", and another is
> to discard the write operations on these pages. This
> patch adds a p2m type class, P2M_DISCARD_WRITE_TYPES,
>
>>> On 01.12.14 at 10:24, wrote:
> --- a/xen/common/compat/memory.c
> +++ b/xen/common/compat/memory.c
> @@ -22,27 +22,66 @@ struct get_reserved_device_memory {
> unsigned int used_entries;
> };
>
> -static int get_reserved_device_memory(xen_pfn_t start,
> -
>>> On 01.12.14 at 10:24, wrote:
> We need to make sure all mmio allocation don't overlap
> any rdm, reserved device memory. Here we just skip
> all reserved device memory range in mmio space.
I think someone else already suggested that this and patch 9 should
be swapped, and the BAR allocation b
Hi,
At 21:13 +0800 on 04 Dec (1417724006), Yu Zhang wrote:
> A new p2m type, p2m_mmio_write_dm, is added to trap and emulate
> the write operations on GPU's page tables. Handling of this new
> p2m type are similar with existing p2m_ram_ro in most condition
> checks, with only difference on final
>>> On 04.12.14 at 16:46, wrote:
> On 04/12/14 14:55, Jan Beulich wrote:
> On 04.12.14 at 15:28, wrote:
>>> On 04/12/14 13:49, Jan Beulich wrote:
>>> On 28.11.14 at 16:46, wrote:
> On 28/11/14 15:18, Jan Beulich wrote:
> On 28.11.14 at 14:55, wrote:
>>> The problem is wi
(I've skipped the internal implementation since I don't know what's
required to fulfil soft reset.)
On Wed, Dec 03, 2014 at 06:16:20PM +0100, Vitaly Kuznetsov wrote:
[...]
> + libxl__domain_create_state *dcs);
>
> /* Each time the dm needs to be saved, w
1 - 100 of 152 matches
Mail list logo
