sed card. It was introduced by a Jan 10 commit post rc7
(sorry, don't have the details right now - my laptop died yesterday).
A bugzilla has already been opened.
Nigel
This message was sent using IMP, the Internet Messaging
.
Could these patches also help with hibernation issues? I'm trying
x86_64+NO_HZ, and seeing activity delayed during the atomic copy and
afterwards until I manually generate interrupts (by pressing keys).
Regards,
Nigel
--
To unsubscribe from this list: send the line "unsubscribe linux-kern
v_name, port->line);
>>
>> ops->shutdown(port);
>> }
>>
>
> Is printk() enough for 'we've just lost your data' condition? Maybe we
> should abort suspend if we can't drain fifo?
No way. Think about this from a
ng. Something seems to help, but I haven't
managed to identify what yet. I don't think it was the patch appended
because I'm on UP. If you care, I'll see if I can find the time to look
more carefully.
Nigel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
ver - what if the port that is sticking
> is the console - don't we recurse and die ?
I don't know, but I'd argue that we shouldn't die. Things should be as
robust as possible.
Regards,
Nigel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&quo
d the commands when
we're ready to shutdown. It would probably be useful whether or not your
hibernating (if not, sending the commands could always be made an option).
Regards,
Nigel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Hi Michael.
Michael Tokarev wrote:
Nigel Cunningham wrote:
[]
That should be doable. How is your UPS connected? Presumably, with some
modifications to the appropriate driver, we could send the commands when
we're ready to shutdown. It would probably be useful whether or not your
hibern
d may sleep.
*/
int suspend_devices_and_enter(suspend_state_t state)
{
@@ -341,6 +349,8 @@ static inline int valid_state(suspend_st
* happen when we wake up.
* Then, do the setup for suspend, enter the state, and cleaup (after
* we've woken up).
+ *
+ * Needs to b
From 037d9b44c9a18e6c2e3dedde2b8391215accc236 Mon Sep 17 00:00:00 2001
From: Nigel
Date: Mon, 31 Dec 2012 10:58:54 +1100
Subject: [PATCH] Add support for DMI matching in calculating RTC_ALWAYS_BCD.
The Sony Vaio VPCSE15FG needs RTC_ALWAYS_BCD to be false rather than the
otherwise universal
From b41864867464bfe0e2d114528bc9b39e2d9f546e Mon Sep 17 00:00:00 2001
From: Nigel Cunningham
Date: Tue, 1 Jan 2013 13:03:50 +1100
Subject: [PATCH] Fix rbd use after free.
This patch addresses Coverity #753114.
The use of ceph_opts in rbd_add is currently confusing - there
are three possible
From b4a7ab768df17e1cda7d0ae8744e986215a644c3 Mon Sep 17 00:00:00 2001
From: Nigel Cunningham
Date: Tue, 1 Jan 2013 13:53:51 +1100
Subject: [PATCH] Remove unused variable in rbd_dev_probe_update_spec.
As an aside to the previous patch, remove the unused local
variable reply_buf in that function
From 68e866b8eac534405ae16b79b7ffd9de05c11c67 Mon Sep 17 00:00:00 2001
From: Nigel Cunningham
Date: Tue, 1 Jan 2013 13:50:22 +1100
Subject: [PATCH] Fix uninitialised variable in rbd_dev_probe_update_spec.
The local variable ret can be used uninitialised in the error path
if the kstrdup at line
ansfer
between kernels?).
I'd love it if kexec really was the panacea to the freezer issues, but
problems like these make me think it isn't a viable solution.
Nigel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAI
Hi.
Matthew Garrett wrote:
On Thu, Feb 21, 2008 at 09:45:02AM +1100, Nigel Cunningham wrote:
- people keep talking about hibernating to an ext3 fs mounted on fuse as
a limitation of the freezer. To do that with kexec, you're still going
to have to bmap the ext3 fs and pass the block lis
Hi.
Greg KH wrote:
On Thu, Feb 21, 2008 at 11:40:06AM +1100, Nigel Cunningham wrote:
Hi.
Matthew Garrett wrote:
On Thu, Feb 21, 2008 at 09:45:02AM +1100, Nigel Cunningham wrote:
- people keep talking about hibernating to an ext3 fs mounted on fuse as
a limitation of the freezer. To do that
Hi.
Matthew Garrett wrote:
On Thu, Feb 21, 2008 at 11:40:06AM +1100, Nigel Cunningham wrote:
Matthew Garrett wrote:
No, with a freezer-based model you can basically *never* suspend to
anything related to FUSE or a userspace USB device or anything involving
userspace iSCSI initiators or
Hi Greg.
Greg KH wrote:
On Thu, Feb 21, 2008 at 12:17:06PM +1100, Nigel Cunningham wrote:
Hi.
Greg KH wrote:
On Thu, Feb 21, 2008 at 11:40:06AM +1100, Nigel Cunningham wrote:
Hi.
Matthew Garrett wrote:
On Thu, Feb 21, 2008 at 09:45:02AM +1100, Nigel Cunningham wrote:
- people keep talking
in the line above - it should be something like "it makes the PC's
speaker beep as soon as" ('on PC speaker' isn't right).
Sorry for not getting that last time.
Nigel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
text switches.
Second, the scheduler should not penalize the preempted task for being
preempted, so that it should usually get to continue running as soon as
the preempting task is descheduled, which is at most one timeslice for
timesharing tasks.
Nigel Gamble[EMA
re was a concern that it was not practical to have
any sort of lock in the read-side code path and the write side was not
time critical.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
MontaVista Software
h as
> > module unloading, where there was a concern that it was not
> > practical to have any sort of lock in the read-side code path and
> > the write side was not time critical.
>
> True, but only if the synchronize_kernel() implementa
ssible delays in such cases. How's this
> going to work for Linux?
The same way everything works for Linux: with enough people around the
world interested in and working on these problems, they will be fixed.
Nigel Gamble[EMAIL
ed = 1;
#endif
}
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
MontaVista Software [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
roblem.
Try running xmms as root with the "Use realtime priority when available"
option checked. If the distortion is because xmms isn't getting enough
CPU time, then running it at a realtime priority will fix it.
Nigel Gamble[EMAIL PROTEC
,
I didn't realise you were still working on this. Did you know that
I am also? Our most recent version is at:
ftp://ftp.mvista.com/pub/Area51/preemptible_kernel/
although I have yet to put up a 2.4.0-prerelease patch (coming soon).
We should probably pool our efforts on this for 2.5.
od enough for most audio apps.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
by definition, disables kernel preemption without the need
to set a no-preempt flag) to protect regions where the lock is held
for a maximum of around 100us, and to use a sleeping mutex lock for
longer regions. This is what I'm working towards.
Nigel Gamble
orking on a new implementation that also does priority inheritance,
to avoid the priority inversion problem, and that does the minimum
necessary context switches.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
On Thu, 4 Jan 2001, Andi Kleen wrote:
> On Thu, Jan 04, 2001 at 01:39:57PM -0800, Nigel Gamble wrote:
> > Experience has shown that adaptive spinlocks are not worth the extra
> > overhead (if you mean the type that spin for a short time
> > and then decide to sleep).
bably between 1% and 10% of the
total context switches per second. And it's certainly interesting to me
that I can listen to MP3s without interruption now, while doing a kernel
build!
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA.
n the running process sleeps (voluntarily
or when it has to wait for something) or exits. This is the case in
both of the fully preemptible kernels which I've worked on (IRIX and
REAL/IX).
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA.
>
> If so, it's no great surprise that performance dropped given that we replaced
> a spinlock (albeit one guarding somewhat more than the critical section) with
> a semaphore.
>
> Tim
>
> --
> Tim Wright - [EMAIL PROTECTED] or [EMAIL PROTECTED] or [EMAIL PROT
On Sat, 13 Jan 2001, Andrew Morton wrote:
> Nigel Gamble wrote:
> > Spinlocks should not be held for lots of time. This adversely affects
> > SMP scalability as well as latency. That's why MontaVista's kernel
> > preemption patch uses sleeping mutex locks instea
occurred, since we won't
see the interrupt until it's safe to do the preemptive resched.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
-
To unsubscribe from this list: send the line "unsubscrib
On Sat, 20 Jan 2001 [EMAIL PROTECTED] wrote:
> Let me just point out that Nigel (I think) has previously stated that
> the purpose of this approach is to bring the stunning success of
> IRIX style "RT" to Linux. Since some of us believe that IRIX is a virtual
> handbook o
latency, we should just use his so-called "RTLinux" environment
for low-latency tasks. RTLinux is not Linux, it is a separate
environment with a separate, limited set of APIs. You can't run XMMS,
or any other existing Linux audio app in RTLinux. I want a low-latency
Linux, not just anothe
aths are now dominated by the big
kernel lock, which we hope can be completely eliminated in 2.5
by finer grained locks.
(I will be at the Linux Real-Time Workshop in Orlando next week, and
may not be able to access my work email address ([EMAIL PROTECTED]),
which is why I'm posting this fr
@@
mntput(p);
return dentry;
}
+ spin_unlock(&dcache_lock);
dput(d);
mntput(p);
+ spin_lock(&dcache_lock);
}
spin_unlock(&dcache_lock);
Nigel Gamble
MontaVista Software
-
To unsu
ot of operating systems already use.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMA
You could use a semaphore for this. Initialize it to 0, then call
down() from the ioctl, and up() from the interrupt handler. If the
up() happens before the down(), the down() won't go to sleep.
Nigel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
ment priority
inheritance, until this type of starvation scenario occured!
I'm working on making the linux kernel fully preemptible (as I
did for IRIX when I used to work at SGI), and will need
priority inheritance mutexes to enable real-time behavior for
SCHED_FIFO and SCHED_RR tasks. So someon
sequence valid?
> spin_lock_irqsave(a,b);
> spin_lock_irqsave(c,d);
Yes, as long as it is followed by:
spin_unlock_irqrestore(c, d);
spin_unlock_irqrestore(a, b);
Nigel Gamble[EMAIL PROTECTED]
Mountai
o
move them into sched.h, like d_path(), as I don't want to make it more
difficult to apply kernel patches to my kernel source tree.)
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
diff -Nur 2.4.2/CRED
the down and up calls are made by different threads. The former
use is a "lock", while the latter down() use is a "potentially blocking
function" in terms of your question. I don't know how easy it would be
for your analysis tools to distinguish between them.
Nigel G
e need to enter the page fault handler with
interrupts disabled to protect the cr2 register. The interrupt state is
restored immediately after cr2 has been saved. Otherwise, an interrupt
could cause the faulting thread to be preempted, and the new thread
could also fault,
ed the generated code)
The other cases are not very common, as they only happen if a task is
preempted during the short time that it is running while in the process
of changing state while going to sleep or waking up, so the default case
is probably OK for them; and I'd
te current cpu, reschedule */
> while ((current->cpus_allowed &= ~(1 << smp_processor_id())) != 0)
> schedule();
>
> /* Back to normal. */
> current->cpus_allowed = cpus_allowed;
> current->policy = policy;
> current-
f()
only increments current->preempt_count for the preempted task - the
higher priority preempting task that is about to be scheduled will have
a preempt_count of 0.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA.
hat has been preempted is on the run queue and can be
rescheduled on a different CPU, so I can't see how a per-CPU counter
would work. It seems to me that you would need a per run queue
counter, like the example I gave in a previous posting.
Nigel Gamble
others in pgalloc.h. If you know of any other
similar problems on uniprocessors, please let me know.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
MontaVista Software [EMAIL PRO
preemptible kernel, I'm hoping it would be OK to replace
them with a semaphore. Please let me know if this is not the case.
Thanks!
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
MontaVista Sof
documentation) it will become widely understood, as
> it offers scalability and efficiency.
Actually, I agree with you now that I've had a chance to think about
this some more.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA.
r completion */
> down(&sem);
> }
Then consumer could be:
consumer()
{
int i;
start_producers();
/* Wait for 10 items to be produced */
for (i = 0; i < 10; i++)
dow
nt CPU for the
duration that the value of smp_processor_id() is used. Or, if the
critical region is very short, to disable interrupts on the local CPU.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
Mont
On Tue, 20 Mar 2001, Nigel Gamble wrote:
> On Tue, 20 Mar 2001, Rusty Russell wrote:
> > Thoughts?
>
> Perhaps synchronize_kernel() could take the run_queue lock, mark all the
> tasks on it and count them. Any task marked when it calls schedule()
> voluntarily (but not i
ve schedule() point, aren't they, so those tasks are already
safe to access the data we are protecting.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
MontaVista Software
e because of the problem of avoiding
deadlock on the runqueue lock, which the wait queues also use. The
above code in schedule needs the runqueue lock to protect sync_count.
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http:/
code so that it doesn't create new idle tasks
> except during boot.
Would that mean that CPUs that were physically hotplugged wouldn't get
idle threads?
Regards,
Nigel
--
Nigel Cunningham
Software Engineer, Canberra, Australia
http://www.cyclades.com
Bus: +61 (2) 6291 9554;
Hi.
On Tue, 2005-04-05 at 08:46, Nathan Lynch wrote:
> Hi Nigel!
>
> On Tue, Apr 05, 2005 at 08:14:25AM +1000, Nigel Cunningham wrote:
> >
> > On Tue, 2005-04-05 at 01:33, Nathan Lynch wrote:
> > > > Yes, exactly. Someone who understand do_exit please help clean
Hi.
Here, for your consideration, are fixups I still have in my tree after
updating to rc2.
(USB & Framebuffer lists copied because a reasonable number apply
there).
Regards,
Nigel
diff -ruNp
840-combined-pm_message_t-patch.patch-old/drivers/base/power/resume.c
840-combined-pm_messa
Hi.
I got exactly the same thing on both my P4 HT and my Celeron 933 :<.
Trying fresh builds.
Regards,
Nigel
On Wed, 2005-04-06 at 03:26, James Morris wrote:
> On Tue, 5 Apr 2005, James Morris wrote:
>
> > > Surprise, surprise, it works OK here.
> > >
Hi.
On Fri, 2005-04-08 at 22:58, Nigel Cunningham wrote:
> Hi.
>
> I got exactly the same thing on both my P4 HT and my Celeron 933 :<.
> Trying fresh builds.
Actually I tell a lie. I looked at James' trace too quickly. I'll see
what I can collect :>
Nigel
>
hould be fixed in goodness(), if at all possible,
and not leak out as an undocumented magic number into reschedule_idle().
Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/
MontaVista Software
considered important by people who care about security. It also helps
you see why the plugin stuff is useful. Of course plugin isn't really
the right name anymore - it's more of an internal api.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Ca
ants.
No, it's not just you. It's one of those hangovers from the original
code that I hadn't gotten around to cleaning up.
Symbolic constants now in place for the powerdown method too.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calcu
#x27;t really like your own
> logging subsystem.
The first parameter isn't needed anymore - gone. Second one changed to
an enum DONT_CLEAR_BAR | CLEAR_BAR.
Not liking it - that's alright there's some code you've written that I
don't like either :>
Nigel
--
Evolut
going so far as to remove the functionality,
though.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
th
orry - including
this in the patches posted was an oversight.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened.
-
To unsubscribe from this list: send the line "unsubscribe linux-k
afterwards. This function
achieves that.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
ppy to do
both. Andrew?
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
kes the refrigerator much more reliable, even under extreme load.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened.
-
To unsubscribe from this list: send the line "unsubscri
kernel threads before doing the atomic restore.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&quo
this so we actually check the mount time for the
filesystems, but this was a simpler intermediate step.
It may seem superfluous to you, but Suspend2 has over 12,000 users, and
not all of them are expert users. Not everyone gets it right first time.
Regards,
Nigel
--
Evolution.
Enumerate the r
Hi.
On Tue, 2005-07-12 at 16:41, Andrew Morton wrote:
> Nigel Cunningham <[EMAIL PROTECTED]> wrote:
> >
> > First I'll act on feedback from this round. Regarding diffing against
> > -mm, I though Andrew wanted patches against Linus' tree. I'm happy to
Hi
On Mon, 2005-07-11 at 04:22, Pavel Machek wrote:
> On St 06-07-05 12:20:44, Nigel Cunningham wrote:
> > diff -ruNp 621-swsusp-tidy.patch-old/kernel/power/swsusp.c
> > 621-swsusp-tidy.patch-new/kernel/power/swsusp.c
> > --- 621-swsusp-tidy.patch-old/kernel/power/swsusp.c
gt; it, too? ;-).
Yeah. I'm using them already. I must say though that I don't think
sched.h is necessarily the best place for the refrigerator defines. Any
change to those functions and you have to recompile most of the kernel.
Is a refrigerator.h an idea?
Regards,
Nigel
--
Evol
Hi.
On Mon, 2005-07-11 at 04:18, Pavel Machek wrote:
> Hi!
>
> > @@ -0,0 +1,585 @@
> > +/*
> > + * kernel/power/prepare_image.c
> > + *
> > + * Copyright (C) 2003-2005 Nigel Cunningham <[EMAIL PROTECTED]>
> > + *
> > + * This file is re
e extent_chain.
>
> > +#ifndef EXTENT_H
> > +#define EXTENT_H
> > +struct extentchain {
> > + int size; /* size of the extent ie sum (max-min+1) */
> > + int allocs;
> > + int frees;
> > + int debug;
> > + int timesusedoptimisation;
> 10:00:00.0 +1000
> > +++ 617-proc.patch-new/kernel/power/suspend2_core/proc.c2005-07-04
> > 23:14:19.0 +1000
> > @@ -0,0 +1,336 @@
> > +/*
> > + * /kernel/power/proc.c
> > + *
> > + * Copyright (C) 2002-2005 Nigel Cunningham &
> > + * It was originally for compatibility with pre- /proc/suspend
> > + * versions, but has been retained because it makes saving and
> > + * restoring the configuration simpler.
> > + */
>
> Okay, and it is also extremely ugly. Now you have chance to clean it
&g
> > +
> > +/* suspend2_get_nonconflicting_page
> > + *
> > + * Description: Gets a page that will not be overwritten as we copy the
> > + * original kernel page.
> > + */
> > +
> > +unsigned long suspend2_get_nonconflicting_page(vo
On Mon, 2005-07-11 at 09:09, Christoph Hellwig wrote:
> So what is this doing, and is it breaking swsusp support?
Marking at boot time pages that shouldn't be saved. I'm not sure why
Pavel doesn't seem to need it. None of these changes break Pavel's code.
Regards,
Nigel
-
Hi.
On Tue, 2005-07-12 at 19:47, Matthew Garrett wrote:
> Nigel Cunningham <[EMAIL PROTECTED]> wrote:
>
> > When the user has an initrd or initramfs, they're supposed to include
> >
> > echo > /proc/software_suspend/do_resume
>
> This is a differ
s I know about.
Hope it's helpful.
Regards,
Nigel
arch/ppc/platforms/pmac_pic.c |2 +-
arch/ppc/syslib/open_pic.c|2 +-
drivers/base/power/resume.c |8
drivers/base/power/runtime.c |8
dr
Hi.
On Tue, 2005-07-12 at 20:22, Matthew Garrett wrote:
> Nigel Cunningham <[EMAIL PROTECTED]> wrote:
> > On Tue, 2005-07-12 at 19:47, Matthew Garrett wrote:
> >> In general, the kernel does very little to prevent users from shooting
> >> themselves in the foot (o
ssibly userspace ones) unfrozen. Hence we
need to differentiate 'syncthreads'.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened.
-
To unsubscribe from this list: send the line &quo
7;.
>
> OTOH: this is only critical for "niceness", not for
> correctness. Calling sync() before suspend is simply nice thing to do,
> but it is not required in any way. If someone is doing long dd, tough,
> they are going to loose some data if wakeup fails. It is no w
in data loss *if resume fails*. But failing resume
> *always* causes data in running programs to be lost, so I do not see
> that as a problem.
It does for you :>
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed t
riting to a swap file for a long
time (since 1.0), without requiring the filesystem to be mounted when
resuming. We just need to store the bdev and block numbers in the image
header.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be
e solved by modifying every filesystem to support
> some kind of "really read-only!" option. Patches welcome.
>
> 2) suspend2 gets around that by storing absolute positions in on-disk
> image, with resume parameter pointing directly to suspend header.
And a block size. (It
Vinay Venkataraghavan wrote:
Hello,
Hello, *devil's advocate hat on*
I have implemented an bare bones Intrusion detection
system that currently detects scans like open, bouce,
half open etc and a host of other tcp scans.
As an aside, why, we have snort?
I would like to develop this into a
Hi.
The .c gives Gerd Knorr as the maintainer of this file, but no email
address. The MAINTAINERS file doesn't have his name or make it clear who
owns the file. I haven't therefore been able to cc the maintainer.
Tvaudio lacks a refrigerator call. This patch fixes that.
Regards,
Nig
Hi.
This patch removes the few remaining direct invocations of the
refrigerator in 2.6.13-rc3. In drivers/media/video/msp3400.c, it also
shifts the call to after the remove_wait_queue; this seems to be the
more appropriate place.
Regards,
Nigel
Signed-off by: Nigel Cunningham <[EMAIL PROTEC
Hi all.
Here are fixes for four try_to_freeze calls that are still (incorrectly)
using a parameter after the recent try_to_freeze() changes.
Regards,
Nigel
Signed-Off by: Nigel Cunningham <[EMAIL PROTECTED]>
mips/kernel/irixsig.c |2 +-
mips/kernel/signal32.c |2 +-
sh/
ecent switch of Suspend2 to use cryptoapi.
Regards,
Nigel
Kconfig |7 +
Makefile |1
lzf.c| 425 +++
3 files changed, 433 insertions(+)
diff -ruNp 625-crypto-api-work.patch-old/crypto/Kconfig
625-crypto-api-work.patc
Hi Herbert.
Here's a resend of a patch I'm using in Suspend2's new cryptoapi
support, which is needed for us to successfully compress pages using
deflate. It's along the lines of the existing fix in the decompression
code.
Regards,
Nigel
diff -ruNp 190-cryptoapi-defl
Hi.
We've had this feature in Suspend2 for a couple of years and I can
confirm that the approach works, provided that the on-disk filesystem
remains unchanged throughout this. (Useful mainly for kiosks etc).
This is not to say that I've reviewed the code below for correctness.
Regar
Hi.
On Tue, 2005-07-19 at 04:18, Jörn Engel wrote:
> On Mon, 18 July 2005 14:14:53 +1000, Nigel Cunningham wrote:
> >
> > Here's a patch to fix a missing refrigerator call in jffs2.
>^
> You should shorten the
set_current_state(TASK_INTERRUPTIBLE);
>
> See? You are needlessly testing condition twice.
True. I was just concerned that things are messy and inconsistent as
they stand (sometimes we use try_to_freeze and implicitly call
refrigerator(), sometimes we call freezing() and refrigerator). *s
I need to discuss with you at San Jose at the beginning of
> this year.
Yes, I think we did meet. Nice to talk to you again.
Regards,
Nigel
>
> Regards,
> Hiroyuki Machida
>
> Nigel Cunningham wrote:
> > Hi.
> >
> > We've had this feature in S
1 - 100 of 681 matches
Mail list logo
