linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] What to send to Andrew next
Date: Fri, 22 Oct 2004 17:28:48 -0400	[thread overview]
Message-ID: <200410222128.i9MLSmWY005910@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Fri, 22 Oct 2004 18:52:27 +0200." <200410221852.27232.blaisorblade_spam@yahoo.it>

blaisorblade_spam@yahoo.it said:
> 1) FOR INSTANCE, I sent the patch avoiding SIGPROF being touched by
> change_signals(). Why did not you bother at it? 
> 2) copy_from_user_skas() does not make sense. When accessing the page
> tables,  they would be happy to get some locking. If you want to take
> a look to the  4G-4G patch from Ingo Molnar, which must do something
> identical,  

Because I lost them, probably.  I'll go look for them.

> Well, yes, but let's try to be fast on these. They are very good
> patches and  fix also security problems. 

Yeah, syscall-security-* can go in now.  I want to see his test cases before
pushing the signal delivery stuff though.

> And why on x86_64 you do: #define NR_syscalls 1024 

> irq-bits - needed for mainline updates at least since -bk4, but not
> complete. 

?  That's removing code that's duplicated now in -mm but not mainline.

Not sure, that was in the patch I have left over from earlier this year, and
I don't remember why it's there.

Looks like we largely agree.  I'm not going to get to push stuff Andrew-ward 
until Sunday at least, so feel free to send stuff in beforehand.

				Jeff




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-10-22 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22  5:16 [uml-devel] What to send to Andrew next Jeff Dike
2004-10-22 16:52 ` BlaisorBlade
2004-10-22 21:28   ` Jeff Dike [this message]
2004-10-23  3:57     ` BlaisorBlade
2004-10-25  9:05     ` Bodo Stroesser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200410222128.i9MLSmWY005910@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox