On 02/17/16 02:08, Jan Beulich wrote:
> >>> On 17.02.16 at 10:01, wrote:
> > On 02/15/16 04:07, Jan Beulich wrote:
> >> >>> On 15.02.16 at 09:43, wrote:
> >> > On 02/03/16 03:15, Konrad Rzeszutek Wilk wrote:
> >> >> > Similarly to that in KVM/QEMU, enabling vNVDIMM in Xen is composed of
> >> >>
> On February 17, 2016 10:41pm, wrote:
> >>> On 05.02.16 at 11:18, wrote:
> > --- a/xen/drivers/passthrough/vtd/qinval.c
> > +++ b/xen/drivers/passthrough/vtd/qinval.c
> > +if ( pci_hide_device(bus, devfn) )
>
> But now I'm _really_ puzzled: You acquire the exact lock that
> pci_hide
> On February 18, 2016 2:37pm, wrote:
> > From: Xu, Quan
> > Sent: Thursday, February 18, 2016 2:34 PM
> Thanks for your work.
> Kevin
I appreciate your help!:)
Quan
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
> From: Xu, Quan
> Sent: Thursday, February 18, 2016 2:34 PM
>
> > On February 18, 2016 2:16pm, wrote:
> > > From: Xu, Quan
> > > Sent: Wednesday, February 17, 2016 9:38 PM
> > > >
> > > > > BTW, with patch 1/7, I can build Xen successfully( make xen ).
> > > > > To align this rule, I'd better me
> From: Doug Goldstein [mailto:car...@cardoe.com]
> Sent: Wednesday, February 17, 2016 10:38 PM
>
> The function names were inconsistent with acquire and release being
> called acquire_pmu_ownership() and release_pmu_ownship() respectively.
> Function prototypes were available for both spellings s
> On February 18, 2016 2:16pm, wrote:
> > From: Xu, Quan
> > Sent: Wednesday, February 17, 2016 9:38 PM
> > >
> > > > BTW, with patch 1/7, I can build Xen successfully( make xen ).
> > > > To align this rule, I'd better merge patch1/7 and patch 2/7 into a
> > > > large patch.
> > >
> > > Not havin
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, February 17, 2016 9:46 PM
>
> >>> On 17.02.16 at 14:08, wrote:
> > The FPU exception state includes 4 registers:
> >
> > - 64-bit FIP
> > - 16-bit FCS
> > - 64-bit FDP
> > - 16-bit FDS
> >
> > When a CPU takes an FPU exception in l
> From: Xu, Quan
> Sent: Wednesday, February 17, 2016 9:38 PM
> >
> > > BTW, with patch 1/7, I can build Xen successfully( make xen ).
> > > To align this rule, I'd better merge patch1/7 and patch 2/7 into a
> > > large patch.
> >
> > Not having looked at patch 2 yet
> > (I'm about to),
>
> Good n
flight 82983 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82983/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-xsm 6 xen-boot fail REGR. vs. 82764
test-armhf-armhf-libvi
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, February 18, 2016 12:37 AM
>
> No need to do this in two slightly different ways, possibly keeping the
> compiler from folding the code for us.
>
> Signed-off-by: Jan Beulich
Acked-by: Kevin Tian
On Thu, Feb 04, 2016 at 01:51:34AM -0700, Jan Beulich wrote:
> >> >> And I'm afraid there's yet one more issue: If my reading of the
> >> >> SDM is right, then the offsets at which components get saved
> >> >> by XSAVEC / XSAVES aren't fixed, but depend on RFBM (as that's
> >> >> what gets stored i
This allows us to generate a random config which can be used for build
testing random configurations.
Signed-off-by: Doug Goldstein
---
CC: Ian Campbell
CC: Ian Jackson
CC: Jan Beulich
CC: Keir Fraser
CC: Tim Deegan
---
xen/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
d
Add another build target which uses randconfig to randomize the config
file so that we build test more than the default config.
Signed-off-by: Doug Goldstein
---
CC: Ian Campbell
CC: Ian Jackson
CC: Jan Beulich
CC: Keir Fraser
CC: Tim Deegan
---
.travis.yml | 10 ++
1 file changed,
Introduce enum type libxl_checkpointed_stream in IDL.
rename the last argument of migrate_receive from "remus" to
"checkpointed" since the semantics of this parameter has
changed.
NOTE:
libxl_domain_restore_params and domain_create aren't changed here,
checkpointed_stream is still an int. Becaus
Currently struct libxl__domain_suspend_state contains 2 type of states,
one is save state, another is suspend state. This patch separates those
two out.
The motivation of this is that COLO will need to do suspend/resume
continuously, we need a more common suspend state.
After this change, dss stan
Add a new structure remus state, and move concrete layer's private
member to remus state.
it is pure refactoring and no functional changes.
Init interval in libxl__remus_setup(). It is safe to move this initialisation,
because this value is only used for remus, and remus will use this value after
l
We need to enable logdirty on secondary, so we export logdirty_init
for internal use. Rename it to libxl__logdirty_init.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
Acked-by: Ian Campbell
Reviewed-by: Konrad Rzeszutek Wilk
Acked-by: Wei Liu
---
tools/libxl/libxl_dom_save.c | 4 +
This is purely code motion.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
CC: Ian Jackson
Acked-by: Ian Campbell
Reviewed-by: Konrad Rzeszutek Wilk
Acked-by: Wei Liu
---
tools/libxl/Makefile | 2 +-
tools/libxl/libxl_dom.c | 509
After previous refactoring, we are now able to move all remus code
into a separate file libxl_remus.c.
Export following functions for internal use:
- setup/teardown Remus:
* libxl__remus_setup
* libxl__remus_teardown
* libxl__remus_restore_setup
Signed-off-by: Yang Hongyang
Signed-off-by:
This is just tidying up after the "tools/libxl: rename remus device
to checkpoint device" patch automatic renaming.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
Acked-by: Ian Campbell
Reviewed-by: Konrad Rzeszutek Wilk
Acked-by: Wei Liu
---
tools/libxl/libxl_checkpoint_device.c |
we call (init|cleanup)_subkind_nic and (init|cleanup)_subkind_drbd_disk
directly in checkpoint device. Move them to libxl_remus.c, Call them before
calling libxl__checkpoint_devices_setup() or after calling
libxl__checkpoint_devices_teardown().
it is pure refactoring and no functional changes.
Sig
This patchset is Prerequisite for COLO feature. Refer to:
http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
Patch status:
1. Acked patches: patch 2-4, 6-13
2. Reviewd patches: all
3. New patches: none
Note:
1. Patch 1 and 7 is updated according to Wei Liu's comments
2. Patch 2-3 is update
Init stream {read/write} state checkpoint_callback, suspend/resume/checkpoint
callback in Remus setup callback.
There's no functional change, it's just refactoring so that we can move
all remus code into one file.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
CC: Andrew Cooper
CC: Ia
Pass checkpointed_stream from libxl to libxc.
It won't affact legacy migration because legacy migration
won't use this param.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
CC: Andrew Cooper
Reviewed-by: Konrad Rzeszutek Wilk
Acked-by:
This patch is auto generated by the following commands:
1. git mv tools/libxl/libxl_remus_device.c
tools/libxl/libxl_checkpoint_device.c
2. perl -pi -e 's/libxl_remus_device/libxl_checkpoint_device/g'
tools/libxl/Makefile
3. perl -pi -e 's/\blibxl__remus_devices/libxl__checkpoint_devices/g'
t
Before this patch:
1. suspend
a. PVHVM and PV: we use the same way to suspend the guest (send the suspend
request to the guest). If the guest doesn't support evtchn, the xenstore
variant will be used, suspending the guest via XenBus control node.
b. pure HVM: we call xc_domain_shutdown(..., S
Checkpoint device is an abstract layer to do checkpoint.
COLO can also use it to do checkpoint. But there are
still some codes in checkpoint device which touch remus.
This patch and:
tools/libxl: move remus state into a seperate structure
tools/libxl: seperate device init/cleanup from checkpoint
> -Original Message-
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Thursday, February 18, 2016 3:52 AM
> To: Xen-devel
> Cc: Andrew Cooper ; Jan Beulich
> ; Tim Deegan ; Ian Campbell
> ; Tian, Kevin ; Wu, Feng
>
> Subject: [PATCH] xen: Avoid left shifting into a sign
On 2/15/2016 10:55 PM, Meng Xu wrote:
Hi Tianyang,
Thanks for the patch! Great work and really quick action! :-)
I will just comment on something I quickly find out and would look
forwarding to Dario's comment.
On Mon, Feb 8, 2016 at 11:33 PM, Tianyang Chen mailto:ti...@seas.upenn.edu>> wrote
flight 82962 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82962/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-debianhvm-amd64 15 guest-localmigrate/x10 fail REGR.
vs. 82825
Regression
On 02/17/2016 03:24 AM, Ian Campbell wrote:
> On Tue, 2016-02-16 at 14:45 -0700, Jim Fehlig wrote:
>> xl/libxl already supports qemu's network-based block backends
>> such as nbd and rbd. libvirt has supported configuring network
>> disks for long time too. This series marries the two in the
>> lib
The most formal form of xl disk configuration uses key=value
syntax to define each configuration item, e.g.
format=raw, vdev=xvda, access=rw, backendtype=phy, target=disksrc
Change the xl disk formatter to produce this syntax, which allows
target= to contain meta info needed to setup a network-ba
xl/libxl already supports qemu's network-based block backends
such as nbd and rbd. libvirt has supported configuring network
disks for long time too. This series marries the two in the
libxl driver and in the xl<->xml converter. Only rbd supported
is added in this series. Support for other backend
While at it, improve a few comments. No functional change.
Signed-off-by: Jim Fehlig
---
tests/xlconfigtest.c | 34 +++---
1 file changed, 19 insertions(+), 15 deletions(-)
diff --git a/tests/xlconfigtest.c b/tests/xlconfigtest.c
index 4b2f28f..aa53ed8 100644
--- a/t
xl/libxl already supports qemu's network-based block backends
such as nbd and rbd. libvirt has supported configuring such
s for long time too. This patch adds support for rbd
disks in the libxl driver by generating a rbd device URL from
the virDomainDiskDef object. The URL is passed to libxl via th
The target= setting in xl disk configuration can be used to encode
meta info that is meaningful to a backend. Leverage this fact to
support qdisk network disk types such as rbd. E.g. config
such as
can be converted to the following xl
flight 82984 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82984/
Perfect :-)
All tests in this flight passed
version targeted for testing:
xen 3fba5f5ec6bd2c9375735ae09d9615ccb1d7c0d0
baseline version:
xen 483ad4439f7fc71e12
On Wed, Feb 17, 2016 at 05:39:23PM -0500, Boris Ostrovsky wrote:
> Hmm. I think you are right --- I was following wrong branch of the 'if'
> statement. We are always going straight to note_page().
Yap. The is_hypervisor_range() - without the "!" - does note_page().
> Then yes, we should be able t
On 02/17/2016 05:18 PM, Andy Lutomirski wrote:
On Wed, Feb 17, 2016 at 2:03 PM, Borislav Petkov wrote:
On Wed, Feb 17, 2016 at 04:21:56PM -0500, Boris Ostrovsky wrote:
That's exactly the point: if something is mapped it's an error for a
non-PV kernel.
How would something be mapped there? __PA
On Wed, Feb 17, 2016 at 11:03:04PM +0100, Borislav Petkov wrote:
> On Wed, Feb 17, 2016 at 04:21:56PM -0500, Boris Ostrovsky wrote:
> > That's exactly the point: if something is mapped it's an error for a
> > non-PV kernel.
>
> How would something be mapped there? __PAGE_OFFSET is
> 0x8800
On 02/17/2016 05:03 PM, Borislav Petkov wrote:
On Wed, Feb 17, 2016 at 04:21:56PM -0500, Boris Ostrovsky wrote:
That's exactly the point: if something is mapped it's an error for a
non-PV kernel.
How would something be mapped there? __PAGE_OFFSET is
0x8800.
Or are you thinking abou
On Wed, Feb 17, 2016 at 2:03 PM, Borislav Petkov wrote:
> On Wed, Feb 17, 2016 at 04:21:56PM -0500, Boris Ostrovsky wrote:
>> That's exactly the point: if something is mapped it's an error for a
>> non-PV kernel.
>
> How would something be mapped there? __PAGE_OFFSET is
> 0x8800.
>
> O
On Wed, Feb 17, 2016 at 04:21:56PM -0500, Boris Ostrovsky wrote:
> That's exactly the point: if something is mapped it's an error for a
> non-PV kernel.
How would something be mapped there? __PAGE_OFFSET is
0x8800.
Or are you thinking about some insanely b0rked kernel code mapping stu
On 02/17/2016 03:49 PM, Borislav Petkov wrote:
On Wed, Feb 17, 2016 at 12:07:13PM -0800, Luis R. Rodriguez wrote:
OK so here's a wiki to keep track of progress of the difference uses:
http://kernelnewbies.org/KernelProjects/remove-paravirt-enabled
It seems we have a resolution one way or anoth
On Wed, Feb 17, 2016 at 12:49 PM, Borislav Petkov wrote:
> On Wed, Feb 17, 2016 at 12:07:13PM -0800, Luis R. Rodriguez wrote:
>> OK so here's a wiki to keep track of progress of the difference uses:
>>
>> http://kernelnewbies.org/KernelProjects/remove-paravirt-enabled
>>
>> It seems we have a reso
On Wed, Feb 10, 2016 at 10:10:34AM +, Malcolm Crossley wrote:
> Currently the ops are X86 only due to a dependency on the
> X86 only B2M implementation.
>
> Foreign ops conform to draft D of PV-IOMMU design.
>
> XSM control been implemented to allow full security control of
> these priviledge
> > ret_t do_iommu_op(XEN_GUEST_HANDLE_PARAM(void) arg, unsigned int count)
>
> Shouldn't this be changed to be pv_iommu_op_t? instead of void?
>
>
> > {
> > -return -ENOSYS;
> > +ret_t ret = 0;
> > +int i;
>
> unsigned int ?
> > +struct pv_iommu_op op;
> > +struct domain
On Wed, Feb 10, 2016 at 10:10:32AM +, Malcolm Crossley wrote:
> Implement above ops according to PV-IOMMU design draft D.
.. which would be great if they were part of this patch series
and you could just: in docs/misc/blah.
>
> Currently restricted to hardware domains only due to RFC status.
On Wed, Feb 17, 2016 at 12:07:13PM -0800, Luis R. Rodriguez wrote:
> OK so here's a wiki to keep track of progress of the difference uses:
>
> http://kernelnewbies.org/KernelProjects/remove-paravirt-enabled
>
> It seems we have a resolution one way or another for all except for
> the use on arch/
flight 82949 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82949/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 guest-saverestorefail never pass
test-armhf-armhf-libvirt 12 migrate-sup
On Fri, Feb 5, 2016 at 5:17 PM, Fengguang Wu wrote:
> On Fri, Feb 05, 2016 at 12:10:56PM -0800, Andy Lutomirski wrote:
>> On Feb 4, 2016 7:11 PM, "Fengguang Wu" wrote:
>> >
>> > Hi Andy,
>> >
>> > CC more people on Xen testing -- in case OSStest already (or plans to)
>> > cover such test case.
>>
Clang-3.8 generates several .data.rel.ro sections when compiling Xen.
c/s eb2952b4 "x86: move alternative.c data fully into .init.*" cited "While at
it also drop the non-local section names from SPECIAL_DATA_SECTIONS - they
can't be safely converted." without any further information, and google is
On Wed, Feb 10, 2016 at 10:10:31AM +, Malcolm Crossley wrote:
> Function does not need to handle shared EPT use of IOMMU as core code
> already handles this.
Could you mention which part of 'core code' handles this?
Also you may want to say this code can only deal with 4K pages but
not with l
On Wed, Feb 10, 2016 at 10:10:30AM +, Malcolm Crossley wrote:
> If IOMMU driver does not implement lookup_page function then it returns
> -ENOMEM.
That is a very odd return code. Could you explain why -ENOMEM?
>
> Returns 0 on success and any other value on failure.
>
> Signed-off-by: Malc
flight 82928 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82928/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 6 xen-build fail REGR. vs. 79037
build-i386-rumpuserxen
On Wed, Feb 10, 2016 at 10:33:24AM +, Malcolm Crossley wrote:
> This RFC series implements the PV-IOMMU interface according to the PV-IOMMU
> design draft D.
>
> The PV-IOMMU interface is currently restricted to being used by the hardware
> domain only as non hardware domain callers have not b
On Wed, Feb 10, 2016 at 10:10:29AM +, Malcolm Crossley wrote:
> Signed-off-by: Malcolm Crossley
> --
> Cc: jbeul...@suse.com
> Cc: andrew.coop...@citrix.com
> Cc: ian.campb...@citrix.com
> Cc: k...@xen.org
> Cc: t...@xen.org
> Cc: xen-devel@lists.xen.org
> ---
> xen/arch/x86/x86_64/compat/ent
On Mon, Feb 1, 2016 at 7:38 AM, Boris Ostrovsky
wrote:
> + pv_info.paravirt_enabled = 1;
As its being discussed we want to remove paravirt_enabled so this
series should not be merged with this:
http://kernelnewbies.org/KernelProjects/remove-paravirt-enabled
Luis
OK so here's a wiki to keep track of progress of the difference uses:
http://kernelnewbies.org/KernelProjects/remove-paravirt-enabled
It seems we have a resolution one way or another for all except for
the use on arch/x86/mm/dump_pagetables.c, is that right? So to be
clear we should not merge mor
On 02/17/2016 02:02 PM, Konrad Rzeszutek Wilk wrote:
On Mon, Feb 15, 2016 at 03:41:41PM +, Andrew Cooper wrote:
On 15/02/16 15:02, Jan Beulich wrote:
On 15.02.16 at 15:53, wrote:
On 15/02/16 14:50, Jan Beulich wrote:
On 15.02.16 at 15:38, wrote:
On 15/02/16 09:20, Jan Beulich wrote:
O
On Wed, Feb 10, 2016 at 10:07:12AM +, Andrew Cooper wrote:
> On 08/02/16 16:36, Ian Campbell wrote:
> > On Mon, 2016-02-08 at 16:23 +, Tim Deegan wrote:
> >> At 13:42 + on 05 Feb (1454679737), Andrew Cooper wrote:
> >>> The type of the pointer to a bitmap is not interesting; it does not
Clang 3.8 notices, and objects because it is undefined behaviour.
"error: shifting a negative signed value is undefined
[-Werror,-Wshift-negative-value]"
Use unsigned constants rather than signed ones.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Tim Deegan
CC: Ian Campbell
CC: Kevi
On Wed, Feb 17, 2016 at 02:14:38PM -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Feb 17, 2016 at 02:58:33PM +, Ian Campbell wrote:
> > By freeing filename (which is either NULL or the previous iteration of
> > this argument). This implements a semantic where the last --pagefile
> > given on the
On 17/02/16 18:02, Doug Goldstein wrote:
> Allow Xenoprof to be fully disabled when toggling the option off.
>
> Signed-off-by: Doug Goldstein
> ---
> CC: Keir Fraser
> CC: Jan Beulich
> CC: Andrew Cooper
>
> change since v3:
> - drop (void)var; from static inlines
> - fix typo that broke build
On Wed, Feb 17, 2016 at 02:58:33PM +, Ian Campbell wrote:
> By freeing filename (which is either NULL or the previous iteration of
> this argument). This implements a semantic where the last --pagefile
> given on the command line takes precedence.
>
> This is the same semantic as the other opt
On Fri, Feb 05, 2016 at 01:42:10PM +, Andrew Cooper wrote:
> This change is purely scaffolding to reduce the complexity of the following
> three patches.
Keep in mind that the patches may not be applied right after this.
It would be easier to jus spell out the three patches.
On Mon, Feb 15, 2016 at 03:41:41PM +, Andrew Cooper wrote:
> On 15/02/16 15:02, Jan Beulich wrote:
> On 15.02.16 at 15:53, wrote:
> >> On 15/02/16 14:50, Jan Beulich wrote:
> >> On 15.02.16 at 15:38, wrote:
> On 15/02/16 09:20, Jan Beulich wrote:
> On 12.02.16 at 18:42,
On 17/02/16 16:38, Jan Beulich wrote:
> Afaict this was never necessary on a 64-bit hypervisor, and was instead
> just blindly cloned over from 32-bit code: We don't fiddle with (and
> hence don't reload) any of DS, ES, FS, or GS, and an exception on IRET
> itself can equally well be reported to th
On Thu, Feb 04, 2016 at 02:42:32PM +0800, Norton.Zhu wrote:
> XEN HVM, after it hung, no serial log printed.
> it hang in __pirq_guest_unbind. its call stack as follows:
> (XEN)[] __pirq_guest_unbind+0x36/0x350
> (XEN)[] __pirq_guest_unbind+0x36/0x350
> (XEN)[] do_invalid_op+0x30b/0x3f0
flight 82911 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82911/
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 17/02/16 16:37, Jan Beulich wrote:
> No need to do this in two slightly different ways, possibly keeping the
> compiler from folding the code for us.
>
> Signed-off-by: Jan Beulich
>
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -3103,6 +3103,7 @@ void vmx_vmexit_ha
Allow Xenoprof to be fully disabled when toggling the option off.
Signed-off-by: Doug Goldstein
---
CC: Keir Fraser
CC: Jan Beulich
CC: Andrew Cooper
change since v3:
- drop (void)var; from static inlines
- fix typo that broke build (must have forgotten to do XEN_CONFIG_EXPERT=y make
change s
Convert the xenoprof x86 build time option to Kconfig.
CC: Keir Fraser
CC: Jan Beulich
CC: Andrew Cooper
Reviewed-by: Andrew Cooper
Signed-off-by: Doug Goldstein
Acked-by: Jan Beulich
---
CC: Keir Fraser
CC: Jan Beulich
CC: Andrew Cooper
change since v3:
- move xenoprof entry to the main
On 17/02/16 16:36, Jan Beulich wrote:
> Since we only handle real mode, we need to consider neither non-ring0
> nor IOPL. Also for POPF the mode_iopl() check can really be inside the
> not-ring-0 body.
>
> Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
___
On 17/02/16 16:35, Jan Beulich wrote:
> All branches need to #GP when their target violates the segment limit
> (in 16- and 32-bit modes) or is non-canonical (in 64-bit mode). For
> near branches facilitate this via a zero-byte instruction fetch from
> the target address (resulting in address trans
On 2/17/2016 5:09 PM, Konrad Rzeszutek Wilk wrote:
On Wed, Feb 17, 2016 at 09:33:58AM +0200, Corneliu ZUZU wrote:
This patch series is an attempt to move some of the monitor vm-events code to
the common-side. Done to make it easier to move additional parts that can be
moved to common when ARM-si
On 17/02/16 16:32, Jan Beulich wrote:
> Deal with rIP just like with any other register: Truncate to designated
> width upon entry, write back the zero-extended 32-bit value when
> emulating 32-bit code, and leave the upper 48 bits unchanged for 16-bit
> code.
>
> Signed-off-by: Jan Beulich
Revie
On 17/02/16 16:10, Jan Beulich wrote:
> Re-order code to simplify error cleanup.
>
> Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Hi everyone,
we are rebooting a number of Xen Project services in the next few days to
upgrade operating systems. This means that a few services may be temporarily
unavailable. The following websites are affected and will be done during the
times below. If you notice any issues after the reboot
On Wed, Feb 17, 2016 at 10:20:58AM -0700, Jim Fehlig wrote:
> Signed-off-by: Jim Fehlig
> Acked-by: Ian Campbell
applied
> ---
> docs/misc/xl-disk-configuration.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docs/misc/xl-disk-configuration.txt
> b/docs/misc/xl-di
On Wed, Feb 17, 2016 at 10:20:57AM -0700, Jim Fehlig wrote:
> When dequoting config strings in xlu__cfgl_dequote(), unknown
> characters following a '\', and the '\' itself, are discarded.
> E.g. a disk configuration string containing
>
> rbd:pool/image:mon_host=192.168.0.100\:6789
>
> would be
Hi all
Tools people are in the process of splitting libxenctrl into a set of
stable libraries. One of the proposed libraries is libxendevicemodel
which has a collection of APIs that can be used by device model.
Currently we use QEMU as reference to extract symbols and go through
them one by one.
On 02/17/2016 03:11 AM, Ian Campbell wrote:
> On Wed, 2016-02-17 at 10:05 +, Ian Campbell wrote:
>> On Tue, 2016-02-16 at 20:54 -0700, Jim Fehlig wrote:
>>> When dequoting config strings in xlu__cfgl_dequote(), unknown
>>> characters following a '\', and the '\' itself, are discarded.
>>> E.g.
On 02/17/2016 03:10 AM, Ian Campbell wrote:
> On Tue, 2016-02-16 at 20:54 -0700, Jim Fehlig wrote:
>> target= in disk config can be used to convey arbitrary
>> configuration information to backends. Add a bit more info
>> to xl-disk-configuration.txt to clarify this, including some
>> simple nbd an
Signed-off-by: Jim Fehlig
Acked-by: Ian Campbell
---
docs/misc/xl-disk-configuration.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/misc/xl-disk-configuration.txt
b/docs/misc/xl-disk-configuration.txt
index 6a2118d..29f6ddb 100644
--- a/docs/misc/xl-disk-configurat
target= in disk config can be used to convey arbitrary
configuration information to backends. Add a bit more info
to xl-disk-configuration.txt to clarify this, including some
simple nbd and rbd qdisk configurations.
Signed-off-by: Jim Fehlig
---
docs/misc/xl-disk-configuration.txt | 10 +
When dequoting config strings in xlu__cfgl_dequote(), unknown
characters following a '\', and the '\' itself, are discarded.
E.g. a disk configuration string containing
rbd:pool/image:mon_host=192.168.0.100\:6789
would be dequoted as
rbd:pool/image:mon_host=192.168.0.1006789
Instead of disc
This series contains a few improvments related to libxl's
support for the various qdisk types. Patch1 is a small fix
for libxlu_cfg to error when encountering unknown backslash-
escaped characters instead of silently dropping them. Patch2
is actually unrelated and fixes a typo noticed while reviewi
This was introduced by 97ee1f (~5 years ago), but was probably never
surfaced because most people used regular files as CDROM images, so the PHY
backend was actually never selected. A year ago this was changed, and now
regular RAW files are also handled by the PHY backend, which has made this
bug s
Do the allocation of page tables in a separate function. This will
allow to do the allocation at different times of the boot preparations
depending on the features the kernel is supporting.
Signed-off-by: Juergen Gross
---
grub-core/loader/i386/xen.c | 91
Modify the page table construction to allow multiple virtual regions
to be mapped. This is done as preparation for removing the p2m list
from the initial kernel mapping in order to support huge pv domains.
This allows a cleaner approach for mapping the relocator page by
using this capability.
The
Modern pvops linux kernels support an initrd not covered by the initial
mapping. This capability is flagged by an elf-note.
In case the elf-note is set by the kernel don't place the initrd into
the initial mapping. This will allow to load larger initrds and/or
support domains with larger memory, a
The loader for xen paravirtualized environment is using lots of global
variables. Reduce the number by making them either local or by putting
them into a single state structure.
Signed-off-by: Juergen Gross
---
grub-core/loader/i386/xen.c | 259 +++-
1 fil
The loader for xen paravirtualized environment isn't callable multiple
times as it won't free any memory in case of failure.
Call grub_relocator_unload() as other modules do it before allocating
a new relocator or when unloading the module.
Signed-off-by: Juergen Gross
---
grub-core/loader/i386
Various features and parameters of a pv-kernel are specified via
elf notes in the kernel image. Those notes are part of the interface
between the Xen hypervisor and the kernel.
Instead of using num,bers in the code when interpreting the elf notes
make use of the header supplied by Xen for that pur
Modern pvops linux kernels support a p2m list not covered by the
kernel mapping. This capability is flagged by an elf-note specifying
the virtual address the kernel is expecting the p2m list to be mapped
to.
In case the elf-note is set by the kernel don't place the p2m list
into the kernel mapping
Do the allocation of special pages (start info, console and xenbus
ring buffers) in a separate function. This will allow to do the
allocation at different times of the boot preparations depending on
the features the kernel is supporting.
Signed-off-by: Juergen Gross
---
grub-core/loader/i386/xen
Get actual version of include/xen/xen.h from the Xen repository in
order to be able to use constants defined there.
Signed-off-by: Juergen Gross
---
include/xen/arch-x86/xen-x86_32.h | 22 +++
include/xen/arch-x86/xen-x86_64.h | 8 +--
include/xen/xen.h | 125 +
Do the p2m list allocation of the to be loaded kernel in a separate
function. This will allow doing the p2m list allocation at different
times of the boot preparations depending on the features the kernel
is supporting.
While at this remove superfluous setting of first_p2m_pfn and
nr_p2m_frames as
The Xen hypervisor supports starting a dom0 with large memory (up to
the TB range) by not including the initrd and p2m list in the initial
kernel mapping. Especially the p2m list can grow larger than the
available virtual space in the initial mapping.
The started kernel is indicating the support o
1 - 100 of 248 matches
Mail list logo
