similar to: [PATCH supermin 0/3] Require root= parameter, refactor init.

Displaying 20 results from an estimated 3000 matches similar to: "[PATCH supermin 0/3] Require root= parameter, refactor init."

2017 Apr 25
1
[PATCH supermin v2] init: Support root=UUID=... to specify the appliance disk by volume UUID.
v1 -> v2: - I fixed the end condition of the loop in parse_root_uuid. - Retested. Didn't change the busy wait loop into a function or macro, as per discussion on IRC. Rich.
2017 Apr 19
1
[PATCH supermin] init: Support root=UUID=... to specify the appliance disk by volume UUID.
Instead of specifying a device name (eg. root=/dev/sdb), this permits specifying an ext4 volume UUID (root=UUID=12345678-...). This allows the appliance to be robust against the non-determinism of SCSI device enumeration. --- init/init.c | 226 +++++++++++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 192 insertions(+), 34 deletions(-) diff --git a/init/init.c b/init/init.c
2016 Feb 17
8
[PATCH supermin 0/2] Allow an alternate libc to be used for init.
v1 -> v2: - If we split out the init program into a separate init/ directory, that makes it much easier to build against an alternate libc. I tried to build against uClibc, but uClibc requires an entire build chain, which looked like it was going to be a massive ballache. Rich.
2017 Apr 19
0
[PATCH supermin 2/3] init: Move variable declarations to the top of the function.
No functional change, just change the style to the one used by libguestfs. --- init/init.c | 41 +++++++++++++++++++++++++---------------- 1 file changed, 25 insertions(+), 16 deletions(-) diff --git a/init/init.c b/init/init.c index e3d1107..473a5c5 100644 --- a/init/init.c +++ b/init/init.c @@ -96,6 +96,18 @@ static char line[1024]; int main () { + FILE *fp; + size_t n; + char *root,
2017 Apr 19
0
[PATCH supermin 3/3] init: Refactor for-loop which waits for root device to show up.
--- init/init.c | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/init/init.c b/init/init.c index 473a5c5..a6279b8 100644 --- a/init/init.c +++ b/init/init.c @@ -101,13 +101,19 @@ main () char *root, *path; size_t len; int dax = 0; - uint64_t delay_ns = 250000; + uint64_t delay_ns; int virtio_message = 0; - struct timespec t; int major,
2012 Jun 12
1
[PATCH] Add virtio-scsi support to febootstrap.
This patch is the minimum possible to add virtio-scsi support to febootstrap. Problem: SCSI devices are detected asynchronously after the Linux kernel module is loaded. The usual solutions to this involve scsi_wait_scan (deprecated apparently) or udev. However febootstrap doesn't use udev, and adding it is a ton of work with a very uncertain outcome. So the minimum possible change is to
2017 Apr 19
1
Re: [PATCH supermin 3/3] init: Refactor for-loop which waits for root device to show up.
On Wed, Apr 19, 2017 at 10:57:28AM +0100, Richard W.M. Jones wrote: > + struct timespec t; > +#define NANOSLEEP(ns) do { \ > + t.tv_sec = delay_ns / 1000000000; \ > + t.tv_nsec = delay_ns % 1000000000; \ > + nanosleep (&t, NULL); \ > + } while(0) > + Defining 't' outside its context is a bit
2019 Aug 03
5
[nbdkit PATCH 0/3] More responsive shutdown
We noticed while writing various libnbd tests that when the delay filter is in use, there are scenarios where we had to resort to SIGKILL to get rid of nbdkit, because it was non-responsive to SIGINT. I'm still trying to figure out the best way to add testsuite coverage of this, but already proved to myself that it works from the command line, under two scenarios that both used to cause long
2019 Jul 26
1
[nbdkit PATCH] delay: Avoid numeric overflow
Attempting delay-read=1000 results in no delay whatsoever: 1000 seconds, scaled to milliseconds, stored in int, then subjected to .tv_nsec = (ms * 1000000) % 1000000000 results in .tv_nsec being set to 567587328 thanks to 32-bit overflow, but that in turn results in instant EINVAL failure of nanosleep(). Fix it by diagnosing failure to fit in an int during config, and avoid math that
2011 Oct 03
2
patch: Replace many usleep and some sleep calls with nanosleep
Description: Replace many usleep and some sleep calls with nanosleep. usleep is stated in its manual page as removed by POSIX. Contrary to its predecessors, nanosleep semantics is well defined. The replacement, which is mostly in drivers, is untested. Supplements http://bugs.debian.org/633791. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index:
2003 Mar 17
3
nanosleep() replacement
I put together a nanosleep() for systems without it. Please review/test before I commit. It sems to make UnixWare and Open Server 5 happy. My SCO Open Server 3 box broke so I can't test it there. -------------< cut here >---------------- --- openssh/configure.ac.old 2003-03-09 17:16:43.000000000 -0800 +++ openssh/configure.ac 2003-03-16 15:38:28.520560008 -0800 @@ -1483,6 +1483,8 @@
2016 May 16
3
[PATCH supermin] Add support for a DAX root filesystem.
DAX is explained in detail here: https://lwn.net/Articles/610174/ This patch adds support to supermin for using a DAX root filesystem. The corresponding libguestfs patches will be posted shortly once I've tested them a bit more. This requires qemu >= 2.6. Unfortunately it's not really a win for a few reasons: - Requires enabling ACPI, which slows everything down by hundreds of
2014 Feb 24
2
Re: [Qemu-devel] Adjust disk image migration (NBD)
On Fri, Feb 14, 2014 at 11:58:56AM +0100, Michal Privoznik wrote: > On 14.02.2014 10:40, Joaquim Barrera wrote: > > Hi all, > > > > As I am doing some tests with qemu, I realized that the way it does > > 'migrate -i tcp:DEST:444' is not the same as 'libvirt migrate > > --copy-storage-inc'. Basically qemu uses the same stream as RAM > >
2019 Mar 05
2
[PATCH nbdkit] Add new filter for rate-limiting connections.
For virt-v2v we have been discussing how to limit network bandwidth. The initial discussion has been around how to use cgroups to do this limiting, and that is still probably what we will go with in the end. However this patch gives us another possibility for certain virt-v2v inputs, especially VDDK. We could apply a filter on top of the nbdkit plugin which limits the rate at which it copies
2016 Mar 23
7
[PATCH v4 0/6] tests/qemu: Add program for tracing and analyzing boot times.
v4: - Lots more analysis of the /init script and other parts. - Display a list of the longest to shortest activities. - Rebase on top of current head. Rich.
2005 Feb 24
1
[PATCH] Drop SETGROUPS_NOOP
Hi, the SETGROUPS_NOOP define is used only for Cygwin. But it's also combined with the HAVE_SETGROUPS test in bsd-misc.c. So, since setgroups() exists and is functional in Cygwin, this is actually a noop in the more general sense. The below patch drops that entirely. Corinna Index: acconfig.h =================================================================== RCS file:
2003 Feb 01
1
Build errors on AIX 4.2.1: nanosleep
Hi All. There are still build errors for scp on AIX 4.2.1 due to lack of nanosleep (which you can see them live and in colour at [1]). The attached patch fixes this by using the equivalent nsleep function on AIX if it exists and nanosleep doesn't. The patch is mostly the same as the AIX portion of the previous patch for the nanosleep issue, the major difference being that the #define is in
2009 Feb 03
2
some kind of timeout problem in pbx_spool.c
I am using outgoing call files. I typically see the "ooh something changed / timeout" on a regular bases every second to be exact. Then it stops until some other call event happens. So I "mv" my call file to the outgoing spool directory, I am listening to that message, another call file is "mv"'ed into the directory and something happens to the timeout that its
2003 Jan 25
1
Build failures: nanosleep on Solaris and AIX 4.2.x
Hi All. The recent changes to scp caused build failures on Solaris and AIX 4.2 which showed up on the tinderbox[1]. I mentioned the first to djm in email yesterday but I'm posting after finding the second, in case anyone else has seen similar problems. Solaris' nanosleep is in librt (or libposix4 in older versions) which is not linked. Adding them to configure works fine, however ldd
2014 Mar 13
2
[LLVMdev] Be Careful with Positionally-Encoded Operands (AArch64, Mips, AMDGPU, etc.)
----- Original Message ----- > From: "Tom Stellard" <tom at stellard.net> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Thursday, March 13, 2014 9:46:22 AM > Subject: Re: [LLVMdev] Be Careful with Positionally-Encoded Operands (AArch64, Mips, AMDGPU, etc.) > > On