>>> On 27.04.16 at 21:27, wrote:
> @@ -506,6 +518,37 @@ static int prepare_payload(struct payload *payload,
> }
> }
>
> +sec = xsplice_elf_sec_by_name(elf, ELF_BUILD_ID_NOTE);
> +if ( sec )
> +{
> +n = sec->load_addr;
> +
> +if ( sec->sec->sh_size <= siz
>>> On 29.04.16 at 18:52, wrote:
> On Fri, Apr 29, 2016 at 10:42:06AM -0600, Jan Beulich wrote:
>> >>> On 29.04.16 at 18:34, wrote:
>> > On Fri, Apr 29, 2016 at 10:19:41AM -0600, Jan Beulich wrote:
>> >> >>> On 29.04.16 at 17:06, wrote:
>> >> > On Fri, Apr 29, 2016 at 08:44:48AM -0600, Jan Beuli
>>> On 29.04.16 at 19:23, wrote:
> On Fri, Apr 29, 2016 at 10:38:07AM -0600, Jan Beulich wrote:
>> >>> On 27.04.16 at 21:27, wrote:
>> > @@ -304,6 +338,32 @@ int main(int argc, char **argv)
>> > /*mem_siz = (u32)in64_phdr.p_memsz;*/
>> > mem_siz = (u32)(final_exec_addr - in64_phdr.p_vad
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
drivers/xen/efi.c
between commit:
0ec7ae928a9c ("efi: Remove unnecessary (and buggy) .memmap initialization
from the Xen EFI driver")
from the tip tree and commit:
acb2c923a860 ("XEN: EFI: Move x86 specific codes t
On 4/27/16 8:12 AM, Lars Kurth wrote:
>
>> On 24 Apr 2016, at 02:06, Doug Goldstein wrote:
>>
>> On 4/22/16 9:25 AM, George Dunlap wrote:
>>> On Fri, Apr 22, 2016 at 3:22 PM, Lars Kurth
>>> wrote:
> On 22 Apr 2016, at 15:08, George Dunlap wrote:
>
>
> kconfig for the hyper
This allows 'make debug=n' and 'make debug=y' work as it did previously
but only in the case of the user not having an existing .config file
from a 'make menuconfig'. This is because the command line 'debug' flag
can only be used to set the default value and if the user has already
built up a confi
Convert the 'lock_profile' option to Kconfig as CONFIG_LOCK_PROFILE.
Signed-off-by: Doug Goldstein
---
CC: Stefano Stabellini
CC: Julien Grall
CC: Jan Beulich
CC: Andrew Cooper
---
INSTALL| 1 -
xen/Kconfig.debug | 6 ++
xen/Rules.mk | 2 --
Rough cut at converting the debug options from xen/Rules.mk to Kconfig.
This initial version won't have descriptions for all the different
options in the Kconfig.debug file. If people want to suggest some that
would be great but mostly I'm just looking to confirm that this menu
and the inter-depend
There are a number of debugging options for Xen so the idea is to have a
menu to group them all together. Enabling this menu item will also
disable NDEBUG which will result in more debug prints. This was
previously wired into the 'debug=y' command line option.
Signed-off-by: Doug Goldstein
---
CC
Convert the 'perfc' and 'perfc_arrays' options to Kconfig as
CONFIG_PERF_COUNTERS and CONFIG_PERF_ARRAYS to minimize code changes.
Signed-off-by: Doug Goldstein
---
CC: Jan Beulich
CC: Andrew Cooper
---
INSTALL | 2 --
xen/Kconfig.debug | 13 +
Converts the frame_pointer option to a Kconfig option.
Signed-off-by: Doug Goldstein
---
CC: Andrew Cooper
CC: George Dunlap
CC: Ian Jackson
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC: Stefano Stabellini
CC: Tim Deegan
CC: Wei Liu
---
INSTALL | 1 -
xen/Kconfig.debug | 8
Convert the crash_debug option to Kconfig as CONFIG_CRASH_DEBUG. This
was previously togglable on the command line so this adds a message for
users enabling it from the command line to tell them to enable it from
make menuconfig.
Signed-off-by: Doug Goldstein
---
CC: Jan Beulich
CC: Andrew Coope
Convert 'verbose', which was enabled by 'debug=y' to Kconfig as
CONFIG_VERBOSE_DEBUG which is enabled by default when CONFIG_DEBUG is
enabled.
Signed-off-by: Doug Goldstein
---
CC: Stefano Stabellini
CC: Julien Grall
CC: Jan Beulich
CC: Andrew Cooper
CC: Daniel De Graaf
---
INSTALL
flight 93322 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93322/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-amd64-xl-qemuu-ov
> > +/* The memset is done to catch errors. */
> > +memset(info, 'A', sizeof(*info) * MAX_LEN);
> > +memset(name, 'B', sizeof(*name * MAX_LEN * XEN_XSPLICE_NAME_SIZE));
>
> Did you mean to put the "* MAX_LEN * XEN_XSPLICE_NAME_SIZE" inside the
> sizeof()? Coverity thinks it
On Sun, May 01, 2016 at 07:21:45PM +0100, Wei Liu wrote:
> The length expression should be the same one used in malloc.
>
> CID: 1358947
>
> Signed-off-by: Wei Liu
> ---
> Cc: Ian Jackson
> Cc: Konrad Rzeszutek Wilk
Reviewed-by: Konrad Rzeszutek Wilk
> Cc: Ross Lagerwall
> ---
> tools/mis
On Sun, May 01, 2016 at 06:56:13AM +, Jason Long wrote:
> I used Fedora Server edition with enable "Headless Virtualization" and
> problem Solved.
>
OK, so you re-installed. Good. The problem is that you had the i686
instead of the i686-PAE (or x86_64). The i686 is a kernel built for
machine
On Sun, May 01, 2016 at 07:06:42AM +, Jason Long wrote:
> Hello.
> How can I change "Dom0" settings on my Xen. I guess, I just can change memory
> setting. Am I right?
/etc/default/grub and add the GRUB_CMDLINE_XEN, like:
GRUB_CMDLINE_XEN="dom0_mem=max:7GB loglvl=verbose guest_loglvl=verbose
This is a note to let you know that I've just added the patch titled
x86/mm/xen: Suppress hugetlbfs in PV guests
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
x86-mm-xen-s
This is a note to let you know that I've just added the patch titled
x86/mm/xen: Suppress hugetlbfs in PV guests
to the 4.5-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
x86-mm-xen-s
flight 93314 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93314/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-amd64-xl-qemuu-ov
flight 93300 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93300/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-amd64-xl-qemuu-ov
The length expression should be the same one used in malloc.
CID: 1358947
Signed-off-by: Wei Liu
---
Cc: Ian Jackson
Cc: Konrad Rzeszutek Wilk
Cc: Ross Lagerwall
---
tools/misc/xen-xsplice.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/misc/xen-xsplice.c b/tools/
On Sun, May 01, 2016 at 02:34:18PM +0100, George Dunlap wrote:
[...]
> > +name = malloc(sizeof(*name) * XEN_XSPLICE_NAME_SIZE * MAX_LEN);
[...]
> > +/* The memset is done to catch errors. */
> > +memset(info, 'A', sizeof(*info) * MAX_LEN);
> > +memset(name, 'B', sizeof(*
This run is configured for baseline tests only.
flight 44378 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44378/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-midway 14 guest-stop
flight 93296 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93296/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-libvirt-qcow2 9 debian-di-install fail in 93272 pass in 93296
test-armhf-armhf-libvirt-raw 9 de
On 2016年05月01日 21:26, Matt Fleming wrote:
> On Sun, 01 May, at 11:24:18AM, Shannon Zhao wrote:
>> Because the UEFI params for Dom0 are located under /hypervisor/uefi node
>> instead of /chosen. So it needs to check whether it's a Dom0 then search
>> and parse different node with different params ar
On Wed, Apr 27, 2016 at 8:27 PM, Konrad Rzeszutek Wilk
wrote:
> A simple tool that allows an system admin to perform
> basic xsplice operations:
>
> - Upload a xsplice file (with an unique name)
> - List all the xsplice payloads loaded.
> - Apply, revert, replace, or unload the payload using th
On Sun, 01 May, at 11:24:18AM, Shannon Zhao wrote:
> Because the UEFI params for Dom0 are located under /hypervisor/uefi node
> instead of /chosen. So it needs to check whether it's a Dom0 then search
> and parse different node with different params arrays.
Why can't you search both nodes? Would
flight 93290 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93290/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-amd64-xl-qemuu-ov
flight 93297 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93297/
Perfect :-)
All tests in this flight passed
version targeted for testing:
xen c2994f8632d56e5379e612daa216401477dccbdb
baseline version:
xen 9772c480a71ad38cc2
flight 93284 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93284/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt 14 guest-saverestore fail REGR. vs. 91479
test-amd64-amd64-libvirt-
flight 93272 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93272/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl 15 guest-start/debian.repeat fail in 93256 pass in 93272
test-armhf-armhf-xl-multivcpu 15 g
Hello.
How can I change "Dom0" settings on my Xen. I guess, I just can change memory
setting. Am I right?
Tnx.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
34 matches
Mail list logo