Hi,
This patch registers an UML instance with systemd-machined.
You may need to modify the dbus policy to allow this request
in /etc/dbus-1/system.d/org.freedesktop.machine1.conf
Attached patch crashes the UML kernel, but I've know idea why!
Help is appreciated and feedback is welcome!
diff --gi
Call machined's "CreateMachine" to create a scope unit for the
current uml instance.
Signed-off-by: Thomas Meyer
---
arch/um/Makefile| 4 +-
arch/um/include/shared/os.h | 1 +
arch/um/os-Linux/Makefile | 6 ++-
arch/um/os-Linux/
Hi,
I tried to install the latest Fedora 21 from the Network Install Image
DVD (
https://fedoraproject.org/get-prerelease#server
http://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Alpha/Server/x86_64/iso/Fedora-Server-netinst-x86_64-21_Alpha.iso
)
I did these step to install the
Am Montag, den 29.09.2014, 22:17 +0200 schrieb Richard Weinberger:
> On Mon, Sep 29, 2014 at 7:36 PM, Thomas Meyer wrote:
> > Hi,
> >
> > I tried to install the latest Fedora 21 from the Network Install Image
> > DVD (
> > https://fedoraproject.o
Am Montag, den 29.09.2014, 22:20 +0200 schrieb Richard Weinberger:
> On Mon, Sep 29, 2014 at 8:29 PM, Thomas Meyer wrote:
> > Hi,
> >
> > I get a timeout in the Fedora 21 alpha:
> >
> > [ TIME ] Timed out waiting for device
> > dev-disk-by\x2duuid-008af19d\
Hi,
When you pass an initrd to UML and the size of the initrd is too big for
the current kernel memory, a panic() call is done with the message("Out
of memory").
But this message never hits the stdout as the following stack trace
dumps because there is no current_thread_info() in the UML stack, w
Am Freitag, den 03.10.2014, 10:17 +0200 schrieb Richard Weinberger:
> On Fri, Oct 3, 2014 at 1:21 AM, Thomas Meyer wrote:
> > Hi,
> >
> > When you pass an initrd to UML and the size of the initrd is too big for
> > the current kernel memory, a panic() call is done w
Am Freitag, den 03.10.2014, 10:17 +0200 schrieb Richard Weinberger:
> On Fri, Oct 3, 2014 at 1:21 AM, Thomas Meyer wrote:
> > Hi,
> >
> > When you pass an initrd to UML and the size of the initrd is too big for
> > the current kernel memory, a panic() call is done w
Add a kmsg_dumper, that dumps the kmsg buffer to stderr, when no
console is available.
This an enables the printing of early panic() calls triggered in
uml_postsetup().
Signed-off-by: Thomas Meyer
---
arch/um/drivers/ubd_kern.c | 5 +++--
arch/um/include/shared/os.h | 1 +
arch/um/kernel
atomic_notifier_chain_register() and uml_postsetup() do call kernel code
that rely on the current macro and a valid task_struct resp. thread_info struct.
Signed-off-by: Thomas Meyer
---
arch/um/include/shared/as-layout.h | 1 +
arch/um/kernel/um_arch.c | 15 ++-
arch/um
Add a kmsg_dumper, that dumps the kmsg buffer to stdout, when no
console is available.
This an enables the printing of early panic() calls triggered in
uml_postsetup().
Signed-off-by: Thomas Meyer
---
arch/um/drivers/ubd_kern.c | 5 +++--
arch/um/include/shared/os.h | 1 +
arch/um/kernel
atomic_notifier_chain_register() and uml_postsetup() do call kernel code
that rely on the current macro and a valid task_struct resp. thread_info struct.
Signed-off-by: Thomas Meyer
---
arch/um/include/shared/as-layout.h | 1 +
arch/um/kernel/um_arch.c | 15 ++-
arch/um
#0 balance_dirty_pages_ratelimited (mapping=0x792cc618) at
mm/page-writeback.c:1587
#1 0x600ba54f in do_wp_page (mm=, vma=,
address=, page_table=, pmd
=, orig_pte=..., ptl=) at mm/memory.c:2178
#2 0x600bc986 in handle_pte_fault (flags=,
pmd=, pte=, address=, v
ma=, mm=) at mm/
ints/perf working, now as there is stacktrace
support in uml. An interessting tracepoint would be
TRACE_EVENT(bdi_dirty_ratelimit) or TRACE_EVENT(balance_dirty_pages)
>
> A.
>
> >
> > A.
> >
> > On 13/10/14 22:48, Thomas Meyer wrote:
> >> #0 balance_dirty
Hello,
in UML kernel I get a long cpu using loop in __getnstimeofday()
(kernel/time/timekeeping.c:315) in the call of timespec_add_ns(),
when I left the host kernel suspended to ram for a few hours and resume
again.
this is because it seems like the tk->xtime_sec wasn't updated yet, but
the nsecs
irty" should be a unsigned long.
Two's complement of above value is 332...
I'm not sure what's going on here...
any ideas?
>
> A.
>
>
> On 14/10/14 08:21, Thomas Meyer wrote:
> > Am Dienstag, den 14.10.2014, 07:43 +0100 schrieb Anton Ivanov:
>
Add a kmsg_dumper, that dumps the kmsg buffer to stdout, when no
console is available.
This an enables the printing of early panic() calls triggered in
uml_postsetup().
Signed-off-by: Thomas Meyer
---
diff -r ee0ba83fd81e arch/um/kernel/Makefile
--- a/arch/um/kernel/Makefile Sat Oct 11 18:55
Add TRACE_IRQFLAGS_SUPPORT to UML.
This enables LOCKDEP_SUPPORT and TRACING_SUPPORT.
Signed-off-by: Thomas Meyer
---
diff --git a/arch/um/Kconfig.common b/arch/um/Kconfig.common
index 87bc868..6a33c3a 100644
--- a/arch/um/Kconfig.common
+++ b/arch/um/Kconfig.common
@@ -28,10 +28,9 @@ config PCI
atomic_notifier_chain_register() and uml_postsetup() do call kernel code
that rely on the current macro and a valid task_struct resp. thread_info struct.
Signed-off-by: Thomas Meyer
---
diff --git a/arch/um/include/shared/as-layout.h
b/arch/um/include/shared/as-layout.h
index 41c8c77..ca1843e
Am Sonntag, den 19.10.2014, 17:02 +0100 schrieb Anton Ivanov:
> On 19/10/14 15:59, Thomas Meyer wrote:
> > Am Dienstag, den 14.10.2014, 08:31 +0100 schrieb Anton Ivanov:
> >> I see a very similar stall on writeout to ubd with my patches (easy) and
> >> without (diff
Am 20.10.2014 10:27 schrieb Richard Weinberger :
>
> On Sun, Oct 19, 2014 at 2:39 PM, Thomas Meyer wrote:
> > Hello,
> >
> > in UML kernel I get a long cpu using loop in __getnstimeofday()
> > (kernel/time/timekeeping.c:315) in the call of timespec_add_ns(),
&
Am 20.10.2014 11:28 schrieb Daniel Walter :
>
> - Original Message -
> > From: "Thomas Meyer"
> > To: "user-mode-linux-devel"
> > Sent: Sunday, October 19, 2014 4:14:13 PM
> > Subject: [uml-devel] [PATCH v3 3/3] um: enable trace irq
Am 20.10.2014 um 14:13 schrieb Richard Weinberger:
> On Mon, Oct 20, 2014 at 1:18 PM, Thomas Meyer wrote:
>> Am 20.10.2014 11:28 schrieb Daniel Walter :
>>>
>>> - Original Message -----
>>>> From: "Thomas Meyer"
>>>> To: "u
Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger:
> Am 20.10.2014 um 11:51 schrieb Thomas Meyer:
> >> Hmm, does this always happen?
> >
> > Yes, my single core system seems to trigger this every time after resume
> > from ram.
>
> What is yo
Am Sonntag, den 19.10.2014, 21:35 +0200 schrieb Thomas Meyer:
> Am Sonntag, den 19.10.2014, 17:02 +0100 schrieb Anton Ivanov:
> > On 19/10/14 15:59, Thomas Meyer wrote:
> > > Am Dienstag, den 14.10.2014, 08:31 +0100 schrieb Anton Ivanov:
> > >> I see a very similar st
> Am 29.12.2014 um 10:23 schrieb Toralf Förster :
>
> I do have x86 3 UML guest images, created at a x86 bit Gentoo Linux.
> Now I do have a 64 bit Gentoo Linux (hardened kernel == PAX + grsecurity) and
> tried to run such a guest.
>
> Kernel 3.19-rc1-x is special :
Probably you need this patc
Hi,
Any news. On this?
http://sourceforge.net/p/user-mode-linux/mailman/message/32947218/
http://sourceforge.net/p/user-mode-linux/mailman/message/32947219/
http://sourceforge.net/p/user-mode-linux/mailman/message/32947217/
With kind regards
Thomas
Am Montag, den 26.01.2015, 21:44 +0100 schrieb Richard Weinberger:
> On Sun, Jan 18, 2015 at 1:27 PM, Thomas Meyer wrote:
> > Hi,
> >
> > Any news. On this?
> >
> > http://sourceforge.net/p/user-mode-linux/mailman/message/32947218/
> > http://sourceforg
the kernel message buffer will be outputted to the user, to give a
better hint, of what the failure was.
Signed-off-by: Thomas Meyer
---
arch/um/kernel/Makefile| 2 +-
arch/um/kernel/kmsg_dump.c | 43 +++
arch/um/kernel/um_arch.c | 2 ++
3 files
this early code to generate a valid stacktrace, instead of
crashing.
E.g. when an UML kernel is started with an initrd but too few physical
memory the panic() call get's actually processed.
Signed-off-by: Thomas Meyer
---
arch/um/include/shared/as-layout.h | 1 +
arch/um/kernel/um_arch.c
Print a more sensible message about the minimum physical memory
requirement.
Signed-off-by: Thomas Meyer
---
diff --git a/arch/um/kernel/physmem.c b/arch/um/kernel/physmem.c
index 549ecf3..a91cf05 100644
--- a/arch/um/kernel/physmem.c
+++ b/arch/um/kernel/physmem.c
@@ -63,16 +63,23 @@ void
Print a more sensible message about the minimum physical memory
requirement.
Signed-off-by: Thomas Meyer
---
diff --git a/arch/um/kernel/physmem.c b/arch/um/kernel/physmem.c
index 549ecf3..f7af5e6 100644
--- a/arch/um/kernel/physmem.c
+++ b/arch/um/kernel/physmem.c
@@ -61,18 +61,26 @@ void
Am Freitag, den 03.04.2015, 15:17 +0200 schrieb Geert Uytterhoeven:
> On Fri, Apr 3, 2015 at 1:59 PM, Thomas Meyer wrote:
> > --- a/arch/um/kernel/physmem.c
> > +++ b/arch/um/kernel/physmem.c
> > @@ -61,18 +61,26 @@ void __init setup_physmem(unsigned long start, unsigned
Print a more sensible message about the minimum physical memory
requirement.
Signed-off-by: Thomas Meyer
---
diff --git a/arch/um/kernel/physmem.c b/arch/um/kernel/physmem.c
index 549ecf3..6f20626 100644
--- a/arch/um/kernel/physmem.c
+++ b/arch/um/kernel/physmem.c
@@ -57,22 +57,51 @@ void
Thanks Richard :-)
With kind regards
Thomas
> Am 13.04.2015 um 21:23 schrieb Richard Weinberger
> :
>
>> On Fri, Apr 3, 2015 at 4:51 PM, Thomas Meyer wrote:
>> Print a more sensible message about the minimum physical memory
>> requirement.
>>
>> Signed
Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger:
> Am 20.10.2014 um 11:51 schrieb Thomas Meyer:
> >> Hmm, does this always happen?
> >
> > Yes, my single core system seems to trigger this every time after resume
> > from ram.
>
> What is y
Am Sonntag, den 26.04.2015, 20:32 +0200 schrieb Richard Weinberger:
> On Fri, Apr 24, 2015 at 9:58 PM, Thomas Meyer wrote:
> > Am Montag, den 20.10.2014, 11:56 +0200 schrieb Richard Weinberger:
> >> Am 20.10.2014 um 11:51 schrieb Thomas Meyer:
> >> >
> Am 27.04.2015 um 09:23 schrieb Richard Weinberger
> :
>
Hi Richard,
> mea culpa!
> If I forget a patch, just shout at me.
I crawled through the mailing list, you may want to also check these:
http://sourceforge.net/p/user-mode-linux/mailman/message/32922307/
http://sourceforge.net/p/user-m
Hi,
I did port Anton's v4 patch to v4.1-rc1-56-g3d99e3f and run it the last
two days.
Original v4 from Anton can be found here:
https://sourceforge.net/p/user-mode-linux/mailman/message/32856805/
Issues addressed in v5 version:
- Ported to v4.1-rc1-56-g3d99e3f
- Replaced IRQF_DISABLED with IRQF
Am Samstag, den 02.05.2015, 12:08 +0100 schrieb Anton Ivanov:
> On 02/05/15 10:48, Thomas Meyer wrote:
> > Hi,
> >
> > I did port Anton's v4 patch to v4.1-rc1-56-g3d99e3f and run it the last
> > two days.
> >
> > Original v4 from Anton can be found h
gt;
> A.
>
>
>> On 03/05/15 16:46, Thomas Meyer wrote:
>> Am Samstag, den 02.05.2015, 12:08 +0100 schrieb Anton Ivanov:
>> * This is a per-cpu array. A processor only modifies its entry and it only
>> @@ -204,8 +205,16 @@ void arch_cpu_idle(void)
>>
Hi,
Changes:
- also create posix timer in stub_clone_handler()
- incorporated antons remarks
diff --git a/arch/um/Makefile b/arch/um/Makefile
index 17d4460..a4a434f 100644
--- a/arch/um/Makefile
+++ b/arch/um/Makefile
@@ -130,7 +130,7 @@ export LDS_ELF_FORMAT := $(ELF_FORMAT)
# The wrappers wil
> Am 10.05.2015 um 14:35 schrieb Richard Weinberger
> :
>
>> On Sun, May 10, 2015 at 1:14 AM, Thomas Meyer wrote:
>> Hi,
>>
>> Changes:
>> - also create posix timer in stub_clone_handler()
>> - incorporated antons remarks
>
> Hm, this patch
Am 11.05.2015 7:31 nachm. schrieb Anton Ivanov :
>
> On 11/05/15 18:20, Anton Ivanov wrote:
> > On 11/05/15 18:00, Thomas Meyer wrote:
> >> Hi,
> >>
> >> maybe there is a bug in how the timers are created for all user space
> >> processes.
>
rture" suite now to see if there is
> >> significant difference with relation to other known bugs like the ext4
> >> writeout (my original patch versions seemed to aggravate it).
> >>
> >> I will try to get around to restore my virtual desktop setup ove
Am 11.05.2015 9:42 nachm. schrieb Anton Ivanov :
>
> On 11/05/15 18:41, Thomas Meyer wrote:
> > Am 11.05.2015 7:31 nachm. schrieb Anton Ivanov
> > :
> >> On 11/05/15 18:20, Anton Ivanov wrote:
> >>> On 11/05/15 18:00, Thomas Meyer wrote:
> >>&g
f-by: Thomas Meyer
---
diff --git a/arch/um/Makefile b/arch/um/Makefile
index e4b1a96..43ef190 100644
--- a/arch/um/Makefile
+++ b/arch/um/Makefile
@@ -130,7 +130,7 @@ export LDS_ELF_FORMAT := $(ELF_FORMAT)
# The wrappers will select whether using "malloc" or the kernel allocator.
LI
Am 20.05.2015 12:12 vorm. schrieb Richard Weinberger
:
>
> On Sun, May 17, 2015 at 11:25 AM, Thomas Meyer wrote:
> > Switch the UML clocksource from interval timers to posix interval timers
> > and move to a monotonic timer.
> >
> > This fixes suspend&a
Am Sonntag, den 31.05.2015, 13:15 +0200 schrieb Richard Weinberger:
> Am 20.05.2015 um 07:26 schrieb Thomas Meyer:
> >
> > Am 20.05.2015 12:12 vorm. schrieb Richard Weinberger <
> > richard.weinber...@gmail.com>:
> > >
> > > On Sun, May 17,
Am Sonntag, den 31.05.2015, 23:49 +0200 schrieb Richard Weinberger:
> Am 31.05.2015 um 21:00 schrieb Thomas Meyer:
> > > Ping.
> > > Would be nice to have this patch for the 4.2 merge window.
> >
> > I can provide you the current version of the patch, but I'
Am Sonntag, den 31.05.2015, 20:10 +0100 schrieb Anton Ivanov:
> On 31/05/15 20:00, Thomas Meyer wrote:
> > Am Sonntag, den 31.05.2015, 13:15 +0200 schrieb Richard Weinberger:
> > > Am 20.05.2015 um 07:26 schrieb Thomas Meyer:
> > > > Am 20.05.2015 12:12 vo
Am Donnerstag, den 04.06.2015, 12:04 +0200 schrieb Thomas Meyer:
>
> Hi,
>
> below patch get's rid of all userspace timers.
> When a kernel timer interrupt is received the userspace process of
> the
> corresponding task is signaled via SIGALRM.
> The SIGALRM signal
Hi,
The uml_net network setup "fails" on my computer with:
[ 15.93] helper_wait : waitpid process 11673 failed, errno = 10
[ 15.93] * modprobe tun
* ifconfig tap0 192.168.10.1 netmask 255.255.255.255 up
* bash -c echo 1 > /proc/sys/net/ipv4/ip_forward
[
Am Montag, den 13.07.2015, 15:52 +0200 schrieb Richard Weinberger:
> On Mon, Jul 13, 2015 at 3:41 PM, Thomas Meyer
> wrote:
> > Hi,
> >
> > The uml_net network setup "fails" on my computer with:
> >
> > [ 15.93] helper_wait :
Am Montag, den 13.07.2015, 16:00 +0200 schrieb Richard Weinberger:
> Am 13.07.2015 um 15:58 schrieb Thomas Meyer:
> > Am Montag, den 13.07.2015, 15:52 +0200 schrieb Richard Weinberger:
> > > On Mon, Jul 13, 2015 at 3:41 PM, Thomas Meyer
> > > wrote:
> > >
Am Montag, den 13.07.2015, 16:41 +0200 schrieb Richard Weinberger:
> Am 13.07.2015 um 16:24 schrieb Thomas Meyer:
> > > Yeah. And please add a dump_stack() to figure out where it was
> > > called.
> >
> > I think calling dump_stack() somehow changed the e
Am Montag, den 13.07.2015, 17:11 +0200 schrieb Richard Weinberger:
> Am 13.07.2015 um 17:08 schrieb Thomas Meyer:
> > Am Montag, den 13.07.2015, 16:41 +0200 schrieb Richard Weinberger:
> > > Am 13.07.2015 um 16:24 schrieb Thomas Meyer:
> > > > > Yeah. And please
hang in copy_context_skas0() by disabling signals.
Signed-off-by: Thomas Meyer
---
arch/um/Makefile| 2 +-
arch/um/include/shared/os.h | 15 +-
arch/um/include/shared/skas/stub-data.h | 5 +-
arch/um/include/shared/timer-internal.h | 13 ++
arch/um/ke
Am Mittwoch, den 15.07.2015, 12:12 +0200 schrieb Richard Weinberger:
> On Mon, Jul 13, 2015 at 5:12 PM, Thomas Meyer
> wrote:
> > Am Montag, den 13.07.2015, 17:11 +0200 schrieb Richard Weinberger:
> > > Am 13.07.2015 um 17:08 schrieb Thomas Meyer:
> > > > Am Mo
f-by: Thomas Meyer
---
arch/um/Makefile| 2 +-
arch/um/include/shared/os.h | 15 +-
arch/um/include/shared/skas/stub-data.h | 5 +-
arch/um/include/shared/timer-internal.h | 13 ++
arch/um/kernel/process.c| 6 +-
arch/um/kernel/skas/clo
Am Sonntag, den 09.08.2015, 12:31 +0200 schrieb Richard Weinberger:
> On Tue, Jul 14, 2015 at 1:45 PM, Thomas Meyer
> wrote:
> > Switch the UML clocksource from interval timers to posix interval
> > timers and
> > move to a monotonic timer.
> >
> > Thi
Am Sonntag, den 09.08.2015, 19:57 +0200 schrieb Richard Weinberger:
> On Wed, Jul 15, 2015 at 3:58 PM, Thomas Meyer
> wrote:
> > Am Mittwoch, den 15.07.2015, 12:12 +0200 schrieb Richard
> > Weinberger:
> > > On Mon, Jul 13, 2015 at 5:12 PM, Thomas Meyer
> >
Am 15.08.2015 10:15 vorm. schrieb Richard Weinberger :
>
> Am 09.08.2015 um 19:53 schrieb Thomas Meyer:
> > Switch the UML clocksource from interval timers to posix interval timers
> > and
> > move to a monotonic timer.
> >
> > This fixes suspend&
wrote:
> > On Tue, Aug 18, 2015 at 6:04 PM, Thomas Meyer wrote:
> >> Am 15.08.2015 10:15 vorm. schrieb Richard Weinberger :
> >>> Am 09.08.2015 um 19:53 schrieb Thomas Meyer:
> >>>> Switch the UML clocksource from interval timers to posix interval timer
Am 14.10.2015 11:23 vorm. schrieb Anton Ivanov :
>
> On 14/10/15 09:25, Thomas Meyer wrote:
> > Hello everyone,
> >
> > I would like to finish this patch, but I'm currently very busy. Sorry!
>
> No worries :) I am barely keeping my head above water too :)
Am 31.10.2015 4:39 vorm. schrieb Balaco Baco :
>
> > On Fri, Oct 30, 2015 at 7:29 AM, Balaco Baco wrote:
> > >
> > > On Thu, Oct 29, 2015, at 16:55, Richard Weinberger wrote:
> > >> On Thu, Oct 29, 2015 at 8:46 PM, Balaco Baco wrote:
> > >> >> > > >> > Really!? I wish I had read that somewhe
Am Samstag, den 31.10.2015, 14:54 +0100 schrieb Richard Weinberger:
> On Thu, Oct 29, 2015 at 7:23 AM, Anton Ivanov
> wrote:
> > I got the first patchset to build, it works very well on a single
> > core
> > host or with CPU pinning of the UML - the performance gain is >
> > 25%.
> >
> > However,
Am Samstag, den 31.10.2015, 16:13 +0100 schrieb Richard Weinberger:
> Am 31.10.2015 um 16:10 schrieb Thomas Meyer:
> > Am Samstag, den 31.10.2015, 14:54 +0100 schrieb Richard Weinberger:
> > > On Thu, Oct 29, 2015 at 7:23 AM, Anton Ivanov
> > > wrote:
> > > >
Am Samstag, den 31.10.2015, 16:21 +0100 schrieb Richard Weinberger:
> Am 31.10.2015 um 16:16 schrieb Thomas Meyer:
> > mhh. strange. I didn't see this behaviour on my machine, but my
> > machine
> > is a rare single core system so, likely a race condition while
> >
Am Samstag, den 31.10.2015, 16:30 +0100 schrieb Richard Weinberger:
> Am 31.10.2015 um 16:24 schrieb Thomas Meyer:
> > Am Samstag, den 31.10.2015, 16:21 +0100 schrieb Richard Weinberger:
> > > Am 31.10.2015 um 16:16 schrieb Thomas Meyer:
> > > > mhh. strange. I d
Am 03.11.2015 8:11 vorm. schrieb Anton Ivanov :
>
> On 02/11/15 22:13, Anton Ivanov wrote:
> > On 02/11/15 21:50, Richard Weinberger wrote:
> >> Am 02.11.2015 um 17:16 schrieb Anton Ivanov:
> >>> -void idle_sleep(unsigned long long nsecs)
> >>> +/**
> >>> + * os_idle_sleep() - sleep for a giv
Am Montag, den 09.11.2015, 15:03 + schrieb Anton Ivanov:
> It throws a couple of harmless "epoll del fd" warnings on reboot
> which
> result the fact that disable_fd/enable_fd are not removed in the
> terminal/line code.
>
> These are harmless and will go away once the term/line code gets
>
Am 20.11.2015 3:08 nachm. schrieb Anton Ivanov :
>
> On 20/11/15 13:48, st...@nixia.no wrote:
> > Den 2015-11-20 13:50, skrev Anton Ivanov:
> >> On 20/11/15 12:26, st...@nixia.no wrote:
> > 4. While I can propose a brutal patch for signal.c which sets
> > guards
> > against reentra
Am 31.12.2015 5:06 nachm. schrieb Vegard Nossum :
>
> Similarly to commit fb1770aa78a43530940d0c2dd161e77bc705bdac, with gcc 5
> on Ubuntu and CONFIG_STATIC_LINK=y I was seeing these linker errors:
Hi,
Oops, yes this patch looks good to me. Honestly I did never test the static
link case. Sorry
Hi Vegard,
I like this idea.
With kind regards
Thomas
> Am 02.01.2016 um 03:31 schrieb Vegard Nossum :
>
> If you don't have libpcap or libvdeplug installed, you will get build
> failures when compiling certain files:
>
> arch/um/drivers/vde_user.c:8:24: fatal error: libvdeplug.h: No such fil
Hi,
Mhh. Strange. Do you have a stack trace to call to current thread info which
ends up with a wrong value. I wonder from were it originates.
With kind regards
Thomas
With kind regards
Thomas
> Am 21.05.2016 um 15:51 schrieb Vegard Nossum :
>
> Hi people,
>
> I'm having some trouble with
Am Sonntag, den 22.05.2016, 17:39 +0200 schrieb Vegard Nossum:
> On 21 May 2016 at 20:18, Thomas Meyer wrote:
> >
> > Am 21.05.2016 um 15:51 schrieb Vegard Nossum > om>:
> > >
> > > I'm having some trouble with using current_thread_info() during
&g
Hi,
my kernel log is full with those messages:
any ideas? I have CONFIG_LOCKDEP=y set.
[ 3237.22] [ cut here ]
[ 3237.22] WARNING: CPU: 0 PID: 1445 at mm/mmap.c:1110 vma_merge+0x323/0x3c0
[ 3237.22] Modules linked in:
[ 3237.22] CPU: 0 PID: 1445 Comm: mdad
Am 15. Januar 2017 13:16:22 MEZ schrieb sge...@aol.com:
>Hi,
>
>there seems to be a problem with usermode linux when started
>with an initial ramdisk (argument initrd=file). Here is what
>happens:
>
>
>
>Locating the bottom of the address space ... 0x1000
>Locati
Hi,
with the current rw/linux-next I see a lot of those:
Mai 07 22:01:34 bifrst kernel: [ cut here ]
Mai 07 22:01:34 bifrst kernel: WARNING: CPU: 0 PID: 505 at mm/mmap.c:1112
vma_merge+0x323/0x3c0
Mai 07 22:01:34 bifrst kernel: Modules linked in:
Mai 07 22:01:34 bifrst ke
Zitat von Richard Weinberger :
> Thomas,
>
> On Sun, May 7, 2017 at 1:44 PM, Thomas Meyer wrote:
>> Hi,
Hi,
>>
>> Did anybody try to run UML on the new Windows 10 subsystem for Linux? I
>> wonder what missing functions may hinder to run UML on WSL?
>
&g
> Am 08.05.2017 um 17:05 schrieb Richard Weinberger :
>
> Thomas,
>
>> Am 08.05.2017 um 17:02 schrieb Thomas Meyer:
>> Sadly, UML executable bails out very early. it Looks like WSL is missing
>> some PTRACE stuff:
>>
>> thomas@DESKTOP-DQBDJ0U:/mnt
> Am 08.05.2017 um 17:35 schrieb Richard Weinberger :
>
> Thomas,
>
> Am 08.05.2017 um 17:32 schrieb Thomas Meyer:
>>> We could figure how to report issues to WSL, create self-hosting unit tests
>>> and ask them to add/fix
>>> these features.
>>
> Am 08.05.2017 um 17:40 schrieb Thomas Meyer :
>
>
>> Am 08.05.2017 um 17:35 schrieb Richard Weinberger :
>>
>> Thomas,
>>
>> Am 08.05.2017 um 17:32 schrieb Thomas Meyer:
>>>> We could figure how to report issues to WSL, create self-hosting
Zitat von Richard Weinberger :
> Thomas,
>
> Can you please give the attached patch a try?
Hi,
attached patch work correctly under Linux. But no change under WSL. As
stated in the relevant GH issue, there seems to be far more road
blockers to make UML work under WSL.
With you patch I get u
>From 90c1f4bb11d0ce6fa36051f0d8a94f11580b4b37 Mon Sep 17 00:00:00 2001
From: Thomas Meyer
Date: Tue, 9 May 2017 18:56:28 +0200
Subject: [PATCH] um: Document change_sig and switch to bool type
---
arch/um/include/shared/os.h | 3 ++-
arch/um/os-Linux/main.c | 4 ++--
arch/um/os-Li
Zitat von Richard Weinberger :
> Thomas,
>
> Am 09.05.2017 um 10:15 schrieb Thomas Meyer:
>> attached patch work correctly under Linux. But no change under WSL.
>> As stated in the relevant GH issue, there seems to be far more road
>> blockers to make UML work unde
Hi,
after looking into using userfaultfd for the userspace UML process
page fault handling, I come to the conclusion that userfaultfd
*cannot* be used for above goal as it only operates on mmaped memory
areas.
Am I missing something? What do you think about it?
with kind regards
thomas
Am 13.05.2017 um 12:04 schrieb Richard Weinberger:
> Thomas,
Hi,
> On Sat, May 13, 2017 at 10:10 AM, Thomas Meyer wrote:
>>
>> Hi,
>>
>> after looking into using userfaultfd for the userspace UML process
>> page fault handling, I come to the conclusion that
Also use correct function name spelling (stub_segv_handler) for better
grepping
Signed-off-by: Thomas Meyer
---
arch/um/os-Linux/skas/process.c | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/arch/um/os-Linux/skas/process.c b/arch/um/os-
Linux
Signed-off-by: Thomas Meyer
---
arch/um/kernel/trap.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/um/kernel/trap.c b/arch/um/kernel/trap.c
index 5915887..4e6fcb3 100644
--- a/arch/um/kernel/trap.c
+++ b/arch/um/kernel/trap.c
@@ -183,6 +183,16 @@ void fatal_sigsegv(void
Signed-off-by: Thomas Meyer
---
arch/um/include/shared/skas/stub-data.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/um/include/shared/skas/stub-data.h
b/arch/um/include/shared/skas/stub-data.h
index a9deece..13f404e 100644
--- a/arch/um/include/shared/skas/stub-data.h
+++ b/arch/um
Hi,
as far as I understand everything under os-Linux should be OS specific
and shouldn't rely on kernel functions.
@Richard: What do you think about this patch?
See: https://marc.info/?l=linux-kernel&m=149337493432407&w=2
with kind regards
thomas
--
> Am 17.05.2017 um 03:52 schrieb Masami Hiramatsu :
>
> Hi Thomas,
Hi,
>
> On Tue, 16 May 2017 17:46:47 +0200
> Thomas Meyer wrote:
>
>> Hi,
>>
>> as far as I understand everything under os-Linux should be OS specific
>> and shouldn'
ed scripts/gcc-plugins/latent_entropy_plugin.so
HOSTCXX -fPIC scripts/gcc-plugins/structleak_plugin.o
HOSTLLD -shared scripts/gcc-plugins/structleak_plugin.so
Signed-off-by: Thomas Meyer
---
arch/x86/um/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/um/
This is actually a no-op as all read-only should be read-only in the ELF.
Signed-off-by: Thomas Meyer
---
arch/um/Kconfig.common | 1 +
arch/um/kernel/mem.c | 5 -
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/um/Kconfig.common b/arch/um/Kconfig.common
index 85f6dd2
> Am 21.05.2017 um 23:28 schrieb Richard Weinberger
> :
>
> Thomas,
>
>> On Thu, May 18, 2017 at 12:11 AM, Thomas Meyer wrote:
>> This is actually a no-op as all read-only should be read-only in the ELF.
>
> What problem does this patch fix? Or what is the pu
> Am 22.05.2017 um 20:34 schrieb Richard Weinberger :
>
> Thomas,
>
>> Am 22.05.2017 um 20:14 schrieb Thomas Meyer:
>> It's purely cosmetic; to get rid of the boot message: "This architecture
>> does not have kernel memory protection." in init/main.
> Am 22.05.2017 um 21:37 schrieb Richard Weinberger :
>
> Thomas,
>
>> Am 22.05.2017 um 21:18 schrieb Thomas Meyer:
>>
>>> Am 22.05.2017 um 20:34 schrieb Richard Weinberger :
>>>
>>> Thomas,
>>>
>>>> Am 22.05.2017 um
Hi,
did you see those patches?
https://marc.info/?l=linux-kernel&m=149337486632399&w=2
they were only post to linux-kernel.
With Kind regards
Thomas
--
Check out the vibrant tech community on one of the world's most
1 - 100 of 127 matches
Mail list logo
