* Re: [Qemu-devel] VNC terminal server?
From: Jim C. Brown @ 2006-04-08 19:01 UTC (permalink / raw)
To: qemu-devel
In-Reply-To: <Pine.LNX.4.63.0604082003380.7783@wbgn013.biozentrum.uni-wuerzburg.de>
On Sat, Apr 08, 2006 at 08:24:03PM +0200, Johannes Schindelin wrote:
> IMHO the biggest obstacle to inclusion in mainline QEmu is that the mouse
> support is rather flakey: You have to disable mouse acceleration of the
> guest OS.
>
> I had that cunning plan to write a virtual Wacom tablet, but I just don't
> find the time.
>
> Ciao,
> Dscho
>
Anthony Ligouri has written a patch for wacom support.
However, when I combine this with the -no-sdl-grab patch I still see syncing
issues.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
^ permalink raw reply
* slram
From: Antonio Di Bacco @ 2006-04-08 19:02 UTC (permalink / raw)
To: linuxppc-embedded
Anyone knows what slram driver is meant for?
Bye,
Antonio.
^ permalink raw reply
* Re: Regarding Wrapfs Code - function wrapfs_interpose
From: Erez Zadok @ 2006-04-08 19:00 UTC (permalink / raw)
To: Avishay Traeger; +Cc: UZAIR LAKHANI, linux-fsdevel
In-Reply-To: <1144501811.13374.13.camel@ool-44c32f98.dyn.optonline.net>
In message <1144501811.13374.13.camel@ool-44c32f98.dyn.optonline.net>, Avishay Traeger writes:
> On Fri, 2006-04-07 at 21:51 -0700, UZAIR LAKHANI wrote:
> > I want to find out the purpose of a part of Wrapfs
> > code.
> >
> > The function name is wrapfs_interpose
> >
> > The code is
> >
> > /* check that the lower file system didn't cross a
> > mount point */
> > if (lower_inode->i_sb != SUPERBLOCK_TO_LOWER(sb)) {
> > err = -EXDEV;
> > goto out;
> > }
> >
> > I want to find out what is the purpose of the above
> > check.
>
> Exactly what the comment says - it checks to make sure that we didn't
> cross a mount point. It does this by making sure that the lower-level
> superblock of this lower-level inode is the same as the lower-level
> superblock that we expect (the one used at mount-time). So basically,
> if we see a superblock that is different from the one we usually use, we
> crossed a mount point and so we return an error.
>
> Avishay Traeger
> http://www.fsl.cs.sunysb.edu/~avishay/
More detail.
In its default mode, Wrapfs generates inode numbers by inheriting the inum
of the lower inode: that way we are guaranteed unique inodes, and a fast
operation to generate inodes. But if you cross into a new sb, you could
clash with other inodes that have the same inum (confusing the icache) -- so
the default alg doesn't work unless we prohibit you from crossing into lower
sb's.
Wrapfs supports therefore another mode in which we use iunique() to generate
unique inums. In this mode you *can* cross into new sb's, but the
disadvantage now is that your inums are not persistent (this can mess up
certain tools like tar/find, and NFS).
In Unionfs we implemented yet another alternative (called "imap" or Inode
Map). We generate unique inums, but we store them persistently on the lower
f/s, in a special mapping file. That way we can map our own stacked inums
to the lower ones. So this allows you to cross into any number of sb's, and
it works with NFS (client/server) and with tools like tar and find. Problem
is, performance now suffers each time you have to consult the i-mapping file
to translate b/t upper and lower inums.
Erez.
^ permalink raw reply
* [Qemu-devel] Unified device model
From: Stanislav Shwartsman @ 2006-04-08 19:57 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]
Hello All,
It is not a secret that all open source emulators (QEMU, Bochs, Xen) use the
same emulated devices and mostly copy-paste their emulation one from
another.
I don't know who originally wrote the device models but now Bochs and QEMU
maintain two similar implementations of the same devices.
If one of the teams fixes the implementation or add functionality, another
team mostly copy-paste the changes to their model.
Xen project forked from QEMU and want to stay in touch with Bochs and QEMU
device models and contribute the changes to make the model better.
I am wondering about making unified device models architecture for open
source simulators.
The device models will be used in QEMU, Bochs, Xen and other open source
simulators which would use the device models.
I know about two professional teams working in simulation which would like
to use these device models in their simulator and
could enrich the device library with new devices device interfaces, for
example with AGP and 3D graphics.
Bochs is already in middle of definition of new true pluginable devices
architecture.
In near future Bochs devices will fully separatable from Bochs binary and
when could be developed separately from Bochs.
I call to QEMU developers join to this project and come with their
requirements to plugin architecture.
I don't know if QEMU supports device plugins now but I would like to see
QEMU a part of this idea,
I would like to get single device shared library which could be loaded to
Bochs and QEMU and work perfectly for both.
This will eliminate the need to maintain two separate implementations of the
same devices,
these implementations very fast will converge to single one, C or C++ based,
Bochs or QEMU based, doesn't matter.
I am listening for your opinions !
Thanks,
Stanislav
[-- Attachment #2: Type: text/html, Size: 5766 bytes --]
^ permalink raw reply
* Re: [RFC PATCH] sbp2: remove manipulation of inquiry response
From: Stefan Richter @ 2006-04-08 18:55 UTC (permalink / raw)
To: linux-scsi; +Cc: linux1394-devel
In-Reply-To: <tkrat.d3b4470a9a767dd4@s5r6.in-berlin.de>
I wrote:
> This code became ineffective a few Linux releases ago and is
> apparently not required anyway.
PS: Of my SBP-2 devices, 3 of 3 CD-RWs and 3 of 7 HDDs report a SCSI
level of 0. With and without the patch.
--
Stefan Richter
-=====-=-==- -=-- -=---
http://arcgraph.de/sr/
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply
* Re: [Qemu-devel] VNC terminal server?
From: Johannes Schindelin @ 2006-04-08 18:53 UTC (permalink / raw)
To: Mark Williamson; +Cc: qemu-devel
In-Reply-To: <200604081938.02130.mark.williamson@cl.cam.ac.uk>
Hi,
On Sat, 8 Apr 2006, Mark Williamson wrote:
> The Xen copy of pckbd.c includes a patch to emulate a Summagraphics
> tablet, in order to fix this problem. This is probably reusable for
> QEmu itself.
I even know who wrote it... Donald Dugger. He forwarded it to me also, and
I even think it is part of the RFB patch (too lazy to check right now).
There are two problems:
- configuration is a bitch. For example, X and gpm do not play nice
together. And there is no automatic detection for Summagraphics in kudzu
(which is the automatic hardware detection of Knoppix).
- the patch modifies the PS/2 mouse of QEmu. However, there is no such
thing as a PS/2 Summagraphics. Consequently, all win98 drivers I found did
not detect a Summagraphics device.
Ciao,
Dscho
^ permalink raw reply
* [RFC PATCH] sbp2: remove manipulation of inquiry response
From: Stefan Richter @ 2006-04-08 18:45 UTC (permalink / raw)
To: linux-scsi; +Cc: linux1394-devel
This code became ineffective a few Linux releases ago and is
apparently not required anyway.
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Index: linux-2.6.17-rc1/drivers/ieee1394/sbp2.c
===================================================================
--- linux-2.6.17-rc1.orig/drivers/ieee1394/sbp2.c 2006-04-08 09:43:33.000000000 +0200
+++ linux-2.6.17-rc1/drivers/ieee1394/sbp2.c 2006-04-08 20:40:00.000000000 +0200
@@ -2079,33 +2079,6 @@ static unsigned int sbp2_status_to_sense
}
/*
- * This function is called after a command is completed, in order to do any necessary SBP-2
- * response data translations for the SCSI stack
- */
-static void sbp2_check_sbp2_response(struct scsi_id_instance_data *scsi_id,
- struct scsi_cmnd *SCpnt)
-{
- u8 *scsi_buf = SCpnt->request_buffer;
-
- SBP2_DEBUG_ENTER();
-
- if (SCpnt->cmnd[0] == INQUIRY && (SCpnt->cmnd[1] & 3) == 0) {
- /*
- * Make sure data length is ok. Minimum length is 36 bytes
- */
- if (scsi_buf[4] == 0) {
- scsi_buf[4] = 36 - 5;
- }
-
- /*
- * Fix ansi revision and response data format
- */
- scsi_buf[2] |= 2;
- scsi_buf[3] = (scsi_buf[3] & 0xf0) | 2;
- }
-}
-
-/*
* This function deals with status writes from the SBP-2 device
*/
static int sbp2_handle_status_write(struct hpsb_host *host, int nodeid, int destid,
@@ -2444,13 +2417,6 @@ static void sbp2scsi_complete_command(st
}
/*
- * Take care of any sbp2 response data mucking here (RBC stuff, etc.)
- */
- if (SCpnt->result == DID_OK << 16) {
- sbp2_check_sbp2_response(scsi_id, SCpnt);
- }
-
- /*
* If a bus reset is in progress and there was an error, complete
* the command as busy so that it will get retried.
*/
Index: linux-2.6.17-rc1/drivers/ieee1394/sbp2.h
===================================================================
--- linux-2.6.17-rc1.orig/drivers/ieee1394/sbp2.h 2006-04-08 09:43:32.000000000 +0200
+++ linux-2.6.17-rc1/drivers/ieee1394/sbp2.h 2006-04-08 20:40:00.000000000 +0200
@@ -394,9 +394,8 @@ static int sbp2_link_orb_command(struct
static int sbp2_send_command(struct scsi_id_instance_data *scsi_id,
struct scsi_cmnd *SCpnt,
void (*done)(struct scsi_cmnd *));
-static unsigned int sbp2_status_to_sense_data(unchar *sbp2_status, unchar *sense_data);
-static void sbp2_check_sbp2_response(struct scsi_id_instance_data *scsi_id,
- struct scsi_cmnd *SCpnt);
+static unsigned int sbp2_status_to_sense_data(unchar *sbp2_status,
+ unchar *sense_data);
static void sbp2_parse_unit_directory(struct scsi_id_instance_data *scsi_id,
struct unit_directory *ud);
static int sbp2_set_busy_timeout(struct scsi_id_instance_data *scsi_id);
^ permalink raw reply
* Re: [Bugme-new] [Bug 6357] New: Megaraid driver is more recent for my hardware
From: Andrew Morton @ 2006-04-08 18:41 UTC (permalink / raw)
To: Neela.Kolli; +Cc: qdiverses, bugme-daemon@kernel-bugs.osdl.org, linux-scsi
In-Reply-To: <200604081650.k38Goegv012572@fire-2.osdl.org>
bugme-daemon@bugzilla.kernel.org wrote:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=6357
>
> Summary: Megaraid driver is more recent for my hardware
> Kernel Version: 2.4.8 -> 2.6.16.1
> Status: NEW
> Severity: blocking
> Owner: scsi_drivers-other@kernel-bugs.osdl.org
> Submitter: qdiverses@ifrance.com
>
>
> Most recent kernel where this bug did not occur:
> Distribution: Debian Sarge
> Hardware Environment: Hp Netserver LH3 with Netraid (driver Megaraid)
> Software Environment: Without, I try to update
> Problem Description:
> Hello from France,
> I install with my CD, Debian with a 2.4.8 Kernel. My SCSI card was ok with the
> megaraid driver. I try to update the kernel with the 2.6.16.1 version. But
> after the boot hang on my Scsi card. I read this, a new driver for the megaraid
> is present on the 2.6 kernel. And it doesn't work with my "old" card.
> How can I copy, compile, .... the megaraid driver of 2.4 kernel in 2.6 kenel.
> I start in the world linux and kernel. Can you explain with more sentence
>
^ permalink raw reply
* [lm-sensors] nForce 430 SMBus
From: Jean Delvare @ 2006-04-08 18:42 UTC (permalink / raw)
To: lm-sensors
In-Reply-To: <74ee72ca0604071607l1c1063b2iad93659df1bfe3fa@mail.gmail.com>
Hi Mark,
> > Hey, good work. lease provide the output of (as root):
> > lspci -s 00:0a.1 -xxx
>
> Here it is:
> lspci -s 00:0a.1 -xxx
> 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2)
> 00: de 10 64 02 01 00 b0 00 a2 00 05 0c 00 00 80 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 01 06 00 00 01 07 00 00 00 00 00 00 de 10 84 cb
> 30: 00 00 00 00 44 00 00 00 00 00 00 00 05 01 00 00
> 40: de 10 84 cb 01 00 02 c0 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 01 05 00 00 01 08 00 00 01 09 00 00 00 00 00 00
> 70: 01 00 00 00 00 00 b8 fe 00 00 fe fe 01 20 00 00
OK, that explains it. The driver was looking for the base I/O addresses
at (non-standard registers) 0x50 and 0x54. You have them at (standard
registers) 0x20 and 0x24.
I did some search and it seems that previous nforce4 devices had each
address listed twice (once in the non-standard register and once in the
standard register). Original nforce2 devices had only the non-standard
ones though, which explains why the driver was using them.
So my guess is that Nvidia tried to move to the standard register,
which isn't a bad thing, and kept the old ones around for some times
for compatibility purposes (not a bad idea either.) And your device is
the first one without that compatibility measure, so the driver broke.
I modified the driver so that it'll check the standard register first,
and fallback to the non-standard one when needed (older devices.) Patch
follows:
Add support for the new nForce4 MCP51 (also known as nForce 410 or
430) to the i2c-nforce2 driver. Some code changes were required because
the base I/O address registers have changed in this version. Standard
BARs are now being used, while the original nForce2 chips used
non-standard ones.
Signed-off-by: Jean Delvare <khali at linux-fr.org>
---
drivers/i2c/busses/i2c-nforce2.c | 18 +++++++++++++-----
include/linux/pci_ids.h | 1 +
2 files changed, 14 insertions(+), 5 deletions(-)
--- linux-2.6.17-rc1.orig/drivers/i2c/busses/i2c-nforce2.c 2006-03-27 18:18:57.000000000 +0200
+++ linux-2.6.17-rc1/drivers/i2c/busses/i2c-nforce2.c 2006-04-08 20:29:13.000000000 +0200
@@ -31,6 +31,7 @@
nForce3 250Gb MCP 00E4
nForce4 MCP 0052
nForce4 MCP-04 0034
+ nForce4 MCP51 0264
This driver supports the 2 SMBuses that are included in the MCP of the
nForce2/3/4 chipsets.
@@ -259,6 +260,7 @@
{ PCI_DEVICE(PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE3S_SMBUS) },
{ PCI_DEVICE(PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE4_SMBUS) },
{ PCI_DEVICE(PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_MCP04_SMBUS) },
+ { PCI_DEVICE(PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SMBUS) },
{ 0 }
};
@@ -267,17 +269,20 @@
static int __devinit nforce2_probe_smb (struct pci_dev *dev, int reg,
- struct nforce2_smbus *smbus, char *name)
+ int alt_reg, struct nforce2_smbus *smbus, char *name)
{
u16 iobase;
int error;
- if (pci_read_config_word(dev, reg, &iobase) != PCIBIOS_SUCCESSFUL) {
+ /* Older incarnations of the device used non-standard BARs */
+ if (pci_read_config_word(dev, reg, &iobase) != PCIBIOS_SUCCESSFUL
+ || (!iobase && pci_read_config_word(dev, alt_reg, &iobase)
+ != PCIBIOS_SUCCESSFUL)) {
dev_err(&smbus->adapter.dev, "Error reading PCI config for %s\n", name);
return -1;
}
smbus->dev = dev;
- smbus->base = iobase & 0xfffc;
+ smbus->base = iobase & PCI_BASE_ADDRESS_IO_MASK;
smbus->size = 8;
if (!request_region(smbus->base, smbus->size, nforce2_driver.name)) {
@@ -313,12 +318,15 @@
pci_set_drvdata(dev, smbuses);
/* SMBus adapter 1 */
- res1 = nforce2_probe_smb (dev, NFORCE_PCI_SMB1, &smbuses[0], "SMB1");
+ res1 = nforce2_probe_smb(dev, PCI_BASE_ADDRESS_4, NFORCE_PCI_SMB1,
+ &smbuses[0], "SMB1");
if (res1 < 0) {
dev_err(&dev->dev, "Error probing SMB1.\n");
smbuses[0].base = 0; /* to have a check value */
}
- res2 = nforce2_probe_smb (dev, NFORCE_PCI_SMB2, &smbuses[1], "SMB2");
+ /* SMBus adapter 2 */
+ res2 = nforce2_probe_smb(dev, PCI_BASE_ADDRESS_5, NFORCE_PCI_SMB2,
+ &smbuses[1], "SMB2");
if (res2 < 0) {
dev_err(&dev->dev, "Error probing SMB2.\n");
smbuses[1].base = 0; /* to have a check value */
--- linux-2.6.17-rc1.orig/include/linux/pci_ids.h 2006-04-03 20:50:44.000000000 +0200
+++ linux-2.6.17-rc1/include/linux/pci_ids.h 2006-04-08 18:46:22.000000000 +0200
@@ -1124,6 +1124,7 @@
#define PCI_DEVICE_ID_NVIDIA_QUADRO4_900XGL 0x0258
#define PCI_DEVICE_ID_NVIDIA_QUADRO4_750XGL 0x0259
#define PCI_DEVICE_ID_NVIDIA_QUADRO4_700XGL 0x025B
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SMBUS 0x0264
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_IDE 0x0265
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SATA 0x0266
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SATA2 0x0267
Mark (McKnight), can you please try it too? It should work for you too.
Other users of i2c-nforce2 are invited to test that patch too, just to
make sure I did not accidentally break the older chips.
Thanks,
--
Jean Delvare
^ permalink raw reply
* Re: [Qemu-devel] VNC terminal server?
From: Mark Williamson @ 2006-04-08 18:38 UTC (permalink / raw)
To: qemu-devel
In-Reply-To: <Pine.LNX.4.63.0604082003380.7783@wbgn013.biozentrum.uni-wuerzburg.de>
> On Sat, 8 Apr 2006, Samuel Hunt wrote:
> > It occurs to me that this program would make an excellent basis for a VNC
> > terminal server.
>
> Yeah, something like that has been done already:
> http://libvncserver.sourceforge.net/qemu/qemu-rfb13.patch.gz
>
> There is a notable update since rfb12 (which is a bit out of date
> _cough_): Nis Jorgensen has sent a patch to support scroll mice.
>
> IMHO the biggest obstacle to inclusion in mainline QEmu is that the mouse
> support is rather flakey: You have to disable mouse acceleration of the
> guest OS.
>
> I had that cunning plan to write a virtual Wacom tablet, but I just don't
> find the time.
The Xen copy of pckbd.c includes a patch to emulate a Summagraphics tablet, in
order to fix this problem. This is probably reusable for QEmu itself.
Cheers,
Mark
--
Dave: Just a question. What use is a unicyle with no seat? And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!
^ permalink raw reply
* Re: [Qemu-devel] VNC terminal server?
From: Leonardo E. Reiter @ 2006-04-08 18:37 UTC (permalink / raw)
To: qemu-devel
In-Reply-To: <Pine.LNX.4.63.0604082003380.7783@wbgn013.biozentrum.uni-wuerzburg.de>
Hi Dscho,
this virtual Wacom tablet you refer to... is there a [free or built-in]
Windows 2000/XP driver associated with it that supports either no
acceleration and/or absolute positioning? If so, perhaps I can look at
implementing it in QEMU in my "spare" time ;) Do you have a link to
documentation and/or drivers? If the guest OS can't be easily told to
not do any acceleration and/or use absolute cursor positioning rather
than relative moves, it's not that helpful to have a new type of input
device. I suspect a tablet driver can be easily configured this way
since design people who probably use these devices want perfect
precision between pointer and screen - otherwise they'd probably just
use a mouse/trackball. But you can never be sure how Microsoft (or
Wacom) decided to implement the Windows version of the driver.
The mouse sync solution we have in Win4Lin Pro is okay, but it's a bit
slow and I'd like to do something much cleaner. Of course if I do the
wacom tablet implementation, it will be open source and part of QEMU itself.
Thanks!
- Leo Reiter
Johannes Schindelin wrote:
> I had that cunning plan to write a virtual Wacom tablet, but I just don't
> find the time.
>
> Ciao,
> Dscho
--
Leonardo E. Reiter
Vice President of Product Development, CTO
Win4Lin, Inc.
Virtual Computing from Desktop to Data Center
Main: +1 512 339 7979
Fax: +1 512 532 6501
http://www.win4lin.com
^ permalink raw reply
* [Xenomai-help] Problems using Xenoscope
From: Bernhard Walle @ 2006-04-08 18:29 UTC (permalink / raw)
To: xenomai
Hello,
I have problems using Xenoscope (Xenomai 2.1.0, Xenosim 2.1). The
simulation works, i.e. text messages are printed on the console. I use
the example from
http://www.mail-archive.com/xenomai@xenomai.org.
The problem is that the traces dialog is empty, there are also no items
in the tree, only
- System
-RT/Interfaces
Debugging with GDB seems to work. I used 6.4 and 5.3. I use Debian
GNU/Linux 3.1 with gcc 3.x.
Regards,
Bernhard
--
Wenn schnell schwimmen besser ist als schnell denken, hätten wir auch
Fische bleiben können.
-- Albert Wendt
^ permalink raw reply
* Re: How to create independent branches
From: Jakub Narebski @ 2006-04-08 18:28 UTC (permalink / raw)
To: git
In-Reply-To: <20060408180244.GA4807@xp.machine.de>
Peter Baumann wrote:
> Another question. I'd like to create a totaly independent branch (like
> the "todo" branch in git). Is there a more user friendly way than doing
>
> git-checkout -b todo
> rm .git/refs/heads/todo
> rm .git/index
> rm <all_files_in_your_workdir>
>
> ... hack hack hack ...
> git-commit -a
Wouldn't it be better and more natural to go back to first commit, or even
empty repository state at the beginning, and branch there? Or make separate
repository?
--
Jakub Narebski
Warsaw, Poland
^ permalink raw reply
* Re: Page Migration: Make do_swap_page redo the fault
From: Christoph Lameter @ 2006-04-08 18:25 UTC (permalink / raw)
To: Hugh Dickins; +Cc: akpm, linux-mm
In-Reply-To: <Pine.LNX.4.64.0604081312200.14441@blonde.wat.veritas.com>
On Sat, 8 Apr 2006, Hugh Dickins wrote:
> > do_swap_page may interpret an invalid swap entry without this patch
> > because we do not reload the pte if we are looping back. The page
> > migration code may already have reused the swap entry referenced by our
> > local swp_entry.
>
> Wouldn't you better just remove that !PageSwapCache "Page migration has
> occured" block? Isn't that case already dealt with by the old !pte_same
> check below it?
Right. Since we now replace the swap ptes with ptes pointing to pages
before unlocking the page this is no longer necessary (if the ptes
contents are checked later). That of course means that remove_from_swap()
must always succeed.
Hmmm..,. There are still two other checks for !PageSwapCache after
obtaining a page lock in shmem_getpage() and in try_to_unuse().
However, both are getting to the page via the swap maps. So we need to
keep those.
Signed-off-by: Christoph Lameter <clameter@sgi.com>
Index: linux-2.6/mm/memory.c
===================================================================
--- linux-2.6.orig/mm/memory.c 2006-04-02 21:55:26.000000000 -0700
+++ linux-2.6/mm/memory.c 2006-04-08 11:08:33.000000000 -0700
@@ -1903,12 +1903,6 @@ again:
mark_page_accessed(page);
lock_page(page);
- if (!PageSwapCache(page)) {
- /* Page migration has occured */
- unlock_page(page);
- page_cache_release(page);
- goto again;
- }
/*
* Back out if somebody else already faulted in this pte.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply
* Re: [Qemu-devel] VNC terminal server?
From: Johannes Schindelin @ 2006-04-08 18:24 UTC (permalink / raw)
To: qemu-devel
In-Reply-To: <BAY107-F16FFCE76C42327C842AE508ACE0@phx.gbl>
Hi,
On Sat, 8 Apr 2006, Samuel Hunt wrote:
> It occurs to me that this program would make an excellent basis for a VNC
> terminal server.
Yeah, something like that has been done already:
http://libvncserver.sourceforge.net/qemu/qemu-rfb13.patch.gz
There is a notable update since rfb12 (which is a bit out of date
_cough_): Nis Jorgensen has sent a patch to support scroll mice.
IMHO the biggest obstacle to inclusion in mainline QEmu is that the mouse
support is rather flakey: You have to disable mouse acceleration of the
guest OS.
I had that cunning plan to write a virtual Wacom tablet, but I just don't
find the time.
Ciao,
Dscho
^ permalink raw reply
* Debian Sarge Install??
From: Hal MacArgle @ 2006-04-08 18:13 UTC (permalink / raw)
To: linux-newbie
Debian Sarge; two single layer DVD set bought on eBay.. Packed well
with very nice printed labels and both mounted and read easily with
two separate machines and DVD devices; a HP DVD-300i and Plextor
PK-708A, both relatively new and not overworked..
Tried installing, twice, on a Cyrix III/600mHz CPU; 256mB SDRAM; 8gB
freshly partitioned HD and a c.2000 BIOS.. Both trys stalled on
DVD#1, so I used the distributions "Check the CDRoms Integrity"
program and both failed at different points in the run.. Thought;
must be bad burns???
Not wanting to complain if there is another reason I tried on another
machine: Duron 1.3gHz CPU; 512mB SDRAM; freshly partitioned 12gB on a
40gB HD, this one with the Plextor PK-708A device and c.2000 BIOS...
DVD#1 passed the Integrity run but #2 failed at around 90% of the
checksum run... So no install that machine either.. I got to thinking
that I didn't want to complain to the vendor if the problem was a
single file that I would never need anyway, but how to work around
this; if possible??
Could it be that all files must be perfect to install Debian Sarge??
The vendor charged only pennies above what the blanks cost so can I
really complain?? Are single layer DVD's that critical with data??
TIA...
--
Hal - in Terra Alta, WV/US - Slackware GNU/Linux 10.1 (2.4.29)
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* Re: [Qemu-devel] VNC terminal server?
From: Brad Campbell @ 2006-04-08 18:12 UTC (permalink / raw)
To: qemu-devel
In-Reply-To: <BAY107-F16FFCE76C42327C842AE508ACE0@phx.gbl>
Samuel Hunt wrote:
> It occurs to me that this program would make an excellent basis for a
> VNC terminal server.
>
>
> What I'm basically after is something that I can have several clients
> connect into one server, and the server does all the work and just
> outputs the screen and stuff over the network and recieves the input
> over the network.
>
> VNC does all the I/O that's needed, would it be possible to set Qemu up
> though so it works with VNC as the I/O and simply sits on something like
> Linux as a server, starting a new instance every time another client
> connects?
If you use the vnc patch you kinda get a large part of this already. Major issue is still mouse
synch, but to be honest if you turn of all acceleration in the guest it stays pretty well synced up
now as it is.
I use it all the time on my server to host a win2k session when I need to access windows only
stuff.. Coupled with kqemu it makes for a pretty quick combination.
I *suspect* this is sort of how win4lin terminal server works, though they use funky additions to
keep the mouse sync rock solid and other groovy bits to make life really easy to manage.
I've been meaning to try and get my hands on an eval version to try it out.. as <plug here> the
desktop version makes life dead easy for almost anyone to just install and go. (like it used to with
the old win9x version)
Currently I run gentoo, freebsd-6 and win2k sessions on my server.. they just sit there idle until I
connect to them with vnc.. works a treat.
(server is debian)
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
^ permalink raw reply
* How to create independent branches
From: Peter Baumann @ 2006-04-08 18:02 UTC (permalink / raw)
To: git
In-Reply-To: <7vr749i48s.fsf@assigned-by-dhcp.cox.net>
On Fri, Apr 07, 2006 at 12:18:27PM -0700, Junio C Hamano wrote:
> Peter Baumann <peter.baumann@gmail.com> writes:
>
> > How can I get the inital commit as a patch?
>
> format-patch is designed to get a patch to send to upstream, and
> does not handle the root commit. In your two revisions
> repository, you could do something like this:
>
> $ git diff-tree -p --root master~1
>
> Or more in general:
>
> $ git rev-list master |
> git diff-tree --stdin --root --pretty=fuller -p
>
> BTW, I've been meaning to add --pretty=patch to give
> format-patch compatible output to diff-tree, but haven't got
> around to actually do it. Another thing I've been meaning to do
> is "git log --diff" which is more or less "git whatchanged".
>
Ok. That did it.
Another question. I'd like to create a totaly independent branch (like
the "todo" branch in git). Is there a more user friendly way than doing
git-checkout -b todo
rm .git/refs/heads/todo
rm .git/index
rm <all_files_in_your_workdir>
... hack hack hack ...
git-commit -a
I looked all over the docs, but can't find anything obvious.
-Peter
^ permalink raw reply
* NATed packets only enter the default routing table
From: richard lucassen @ 2006-04-08 17:40 UTC (permalink / raw)
To: netfilter
(copy from lartc mailinglist)
I set up this config:
+------+
-+ ISP1 +--+
+------+ | +-------+
+--+ linux |
+------+ | +-------+
-+ ISP2 +--+
+------+
No problem. Standard setup with two ISP's. Both routed subnets. Default
gateway is ISP1. No magic here.
Now I put a server behind the Linux box. I want the server to be
reachable on an /extra/ IP in the routed subnet of ISP2.
+------+
-+ ISP1 +--+
+------+ | +-------+ +-----------------+
+--+ linux +--+ server 10.0.0.2 |
+------+ | +-------+ +-----------------+
-+ ISP2 +--+
+------+
router ISP2: 1.2.3.1/24
dev ISP2: eth1
Linux box eth1: 1.2.3.2/24
external ip ISP2 for server 10.0.0.2: 1.2.3.3
arp -s 1.2.3.3 aa:bb:cc:dd:ee:ff pub
ip route add 1.2.3.3 via 10.0.0.2
iptables -t nat -A PREROUTING -i eth1 -d 1.2.3.3 -j DNAT --to 10.0.0.2
When pinging 1.2.3.3, the packets get in through eth1 (ok), but the
replies are following the default routing table through eth0 (wrong)
Even a
ip rule add from 1.2.3.3 lookup table_eth1
doesn't change this behaviour. It is working ok when I add the address
1.2.3.3 directly to eth1 (without NAT):
ip a a 1.2.3.3 dev eth1
Why is this?
R.
--
___________________________________________________________________
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.
+------------------------------------------------------------------+
| Richard Lucassen, Utrecht |
| Public key and email address: |
| http://www.lucassen.org/mail-pubkey.html |
+------------------------------------------------------------------+
^ permalink raw reply
* Data about Apple iPod, Mac, Powerbook, iBook needed
From: Stefan Richter @ 2006-04-08 17:36 UTC (permalink / raw)
To: linux1394-user; +Cc: linux-kernel
Hi all,
a number of Apple iPods have buggy firmware which report a wrong disk
size when plugged in. This may lead to I/O errors, making the iPod
inaccessible under Linux. I have been told this happens especially if
the kernel is configured for EFI partition support.
The USB storage driver already contains a workaround for several iPod
models. We need to add the same to the FireWire storage driver (sbp2).
Alas we cannot use the same model IDs like usb-storage to detect whether
a disk is actually an iPod. In particular, sbp2 must be able to
distinguish between iPods and Apple Macs or Powerbooks or iBooks which
are attached to a Linux box in "target disk mode".
Therefore I need help from people who have a FireWire iPod and a Linux
box with FireWire port:
1. Please plug it in via FireWire and report the output of
$ cat /sys/bus/ieee1394/devices/000a27*-0/model_id
and of
$ dmesg | grep "hdwr sectors"
2. If it is an USB/FireWire combo iPod, please also plug it in
via USB and report the output of
$ dmesg | grep "hdwr sectors"
I would also like to know the model of iPod (i.e. generation of iPod)
and the version of the Linux kernel.
I also need help from people who have an Apple Mac or Powerbook or iBook
and a Linux box with FireWire port:
A. On the Linux box, unload the sbp2 driver:
# modprobe -r sbp2
Reload it with the following parameter:
# modprobe sbp2 force_inquiry_hack=1
Also make sure that ohci1394 is loaded. (Check with lsmod. Some
rare host adapters need pcilynx instead oh ohci1394.)
B. Reboot the Apple and hold the "t" key. This boots the Mac into
"target disk mode", i.e. lets it expose its built-in HDD as a
FireWire disk. The "t" key can be released when a big FireWire
symbol is shown on the screen.
C. Connect the Mac and the Linux box via FireWire. The sbp2 driver
should now log in into the Mac, which will be shown in the kernel
log as well as in /proc/scsi/scsi. Please report the output of
$ dmesg | grep firmware_revision
D. The Mac can be unplugged and normally rebooted after this.
Thanks in advance to everyone who takes the time to collect these data.
--
Stefan Richter
-=====-=-==- -=-- -=---
http://arcgraph.de/sr/
^ permalink raw reply
* Re: SuSE 10.0 and it's RPM 4.1.1??
From: Hal MacArgle @ 2006-04-08 17:36 UTC (permalink / raw)
To: Ray Olszewski; +Cc: linux-newbie
In-Reply-To: <4436D44F.8010700@comarre.com>
On 04-07, Ray Olszewski wrote:
> Hal -- I was hoping you'd get feedback from some RPM user who could
> answer your questions directly. As you may recall, I'm exclusively a
> Debian user these days. But I think I may be able to help with some of
> your confusion. And since I gather that Edgar's off-list reply didn't
> cover everything you were looking for, I'll give it a try below.
My original query has been answered by others are well as
this message.. Completely.. I have another one that deserves a
separate post but, meanwhile, will annotate this thread, clipping
much..
> >>>First off, I didn't know what V3 DSA meant,
>
> This is probably a digial signature of some sort,intended to prevent
> package spoofing. About a year ago, Debian added digital authentication
> to its package sites, and as a result, I routinely have to override it
> when installing or upgrading packages from unofficial Debian archives.
> Since you say you were trying to install a package that is not part of
> the offifial distro you were working with, you most likely ran into
> something similar that the RPMers are doing now.
The "crackers" have ruined the INet as I used to know it..
Firewalls and filters really don't work, perfectly.. My 50-100
unwanted messages a day are more easily given the big "D" from Mutt,
IMHO... Safer?? My ISP runs Spam Assassin and I hate to think how
many it might be without it... <grin>
> >>Not sure on this but I believe that SuSE uses a different package system
> >>which is not compatable with Red Hat's.
That seems to be the case unless for very simple code.. Which
and what dependencies seem to be the biggest problem..
> Quick history lesson: Pretty much all distros that are still around
> derive from one of three origins:
>
> 1. Slackware really has no modern descendents, but it is the oldest
> branch that's still active. I believe it still uses .tgz packages
> natively. In a sense, I suppose it (or its anscestors, SLS, Yggdrasil,
> and perhaps others I've forgotten) spawned everything else, but Red Hat
> and Debian diverged so fundamentally from Slackware et al. ... for
> example, abandoning its BSD-style init structure for a SysV structure
> .. that it's hard to see them as derived from Slackware, even beyond
> the difference in package managers.
I keep "coming back" to Slackware and it's a fact that
Patrick is conservative especially since he's battling a serious
illness.. His cause is much strengthened by the existence of
www.linuxpackages.net that contains many, many binary compiles of so
many programs for each Slackware version all in .tgz format... Maybe
when you're not "first" you try harder??
> That said, the fact that two distros use the same package manager does
> NOT mean their packages are interchangeable. All distros have their own
> quirks, in areas like distro-specific kernel patches, slight variation
> in "what goes where" conventions (like /bin vs /usr/bin), customized
> init scripts, vert distinctive installers, and probably more. Package
> naming is not standardized either, so a package from one distro might
> fail to find in a different distro a file it depends on because the
> package name for the file is different.
I now know what others have experienced..
> These days, all good distros cross support one another's package
> managers, either directly or using a "translator" application like
> alien. But resolving dependencies remains messy.
For sure and "alien" is a new one on me to tuck into my grey
cells.. With programs running into millions of lines of code; I think
it works pretty well, bottom line..
> Editors come and go, and I've never found one I like as much as
> VirtualDub, a freeware editor that is Windows only. There are several
> around though ... the term you want to search on is "non-linear editor".
> The Debian-Sid package archive currently lists a gstreamer plugin, kino,
> and pitivi. There are probably others not in Debian.
Since moving video is so complicated; trying each and every
one in turn has to be counter-productive.. I learn as I go... I
fetched Virtual Dub and the author very savvy but I don't want to run
any M$ stuff if I can help it..
> "Streaming" is a pretty open-ended term, so I'm not exactly sure what
> you want to achieve (getting video streams from the Internet? attaching
> a host to your TV set and having it play video stored on a server
> elsewhere on your LAN? multicasting a video stream across your LAN so
> several locations in your home show the same show? putting a DVD in one
> host and having it play back on another? something else?). Be more
> specific here and I'll be happy to give you whatever more advice I can
> (I've been using my Linux server as a TiVo-like backend for several
> years now, but I don't have any significant experience with files
> downloaded from streaming sites on the Internet).
My desires are relatively simple these days: Fetch an
analogue, or view a "movie" from a VHS or DVD player; creat a file
that can be viewed again at a later date; convert this file to a
suite of files that can, in turn, burn a DVD playable on a standard
ubiquitous stand alone DVD player.. Plus, do some simple edits to the
files somewhere, that escapes me at present. I've been able to do
this with much help from you and Chuck so am, now, trying to increase
the quality of the end product, and, in the process, learn more about
digital video.. I need no INet exposure except for downloading
occasional files, especially since we're really rural telco lines so
slow speed thruput is a norm.. I do have a machine in town that can
connect to an ADSL line but for downloads only; bringing the files
home via sneaker net..
> Usually, if you need to install a package from the upstream provider,
> rather than the distro itself, the provider will be fairly specific
> about what distro/version a particular .rpm (or .deb) is designed to
> work with. At least that's my experience with upstream .deb packages.
I've noticed this __trend__ these days but I can't get over
the fact that we used to suffer with dumb terminal/main frames and
celebrated when we were able to get our "work" into our own
building... Plus, IMHO, the longer we are connected the bigger the
cracker profile.. Just an opinion of course. <grin>
> If the upstream provider doesn't have a package that matches your
> distro, you typically have to install from source or from a .tgz (and
> fix any real dependency issues by hand). Again, not really a newbie task
> (yeah, I know you are no more a newbie than I am, Hal, but this *is* a
> beginners' list).
Ray, I've noticed that what I know this week is less than
what I knew last week.. With computers anyway... <BG> Another,
separate subject, post follows; I hope I haven't outlived any
welcomes..
--
Hal - in Terra Alta, WV/US - Slackware GNU/Linux 10.1 (2.4.29)
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* [Qemu-devel] qemu exec.c
From: Paul Brook @ 2006-04-08 17:36 UTC (permalink / raw)
To: qemu-devel
CVSROOT: /sources/qemu
Module name: qemu
Branch:
Changes by: Paul Brook <pbrook@savannah.gnu.org> 06/04/08 17:36:21
Modified files:
. : exec.c
Log message:
Fix typo in previous patch.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/exec.c.diff?tr1=1.75&tr2=1.76&r1=text&r2=text
^ permalink raw reply
* Re: [LARTC] source routing does not work with extra ip addresses
From: richard lucassen @ 2006-04-08 17:33 UTC (permalink / raw)
To: lartc
In-Reply-To: <20060408123017.4a108613.mailinglists@lucassen.org>
On Sat, 8 Apr 2006 11:07:00 -0500
"Martin A. Brown" <martin-lartc@wonderfrog.net> wrote:
> : Now I put a server behind the Linux box. I want the server to be
> : reachable on an /extra/ IP in the routed subnet of ISP2.
>
> Does server have one or two IP addresses? Best solution? Use two
> IP addresses on server.
Hmmm, one for ISP1 and one for ISP2? That would be a nice idea to
workaround this problem :-)
> : When pinging 1.2.3.3, the packets get in through eth1 (ok), but the
> : replies are following the default route through eth0 (wrong)
>
> The problem is routing. Return packets from your server are handled
> in the main routing table. There isn't yet an RPDB entry directing
> traffic from 10.0.0.2 to use table_eth1. Your RPDB entry looks like
> this:
>
> : ip rule add from 1.2.3.3 lookup table_eth1
>
> Try changing this (or adding another rule):
>
> ip rule add from 10.0.0.2 lookup table_eth1
Nope. I already tried that, but no way.
> instead. Now, your server should have Internet access strictly on
> the link handled by ISP2.
No. The packets are returned through ISP1.
> If you would like to handle inbound traffic on both links, then add
> a secondary IP address to your server, and enter another DNAT rule
> which specifies another NAT mapping for the secondary IP.
That's a very nice idea, but packets keep on entering the wrong table
(default), I think it's a bug somewhere in the kernel.
It only works when the ip is direct on the external interface of the
Linuxbox, but as soon as 1 tcp port is translated, the return packets
for that translated port get into the wrong (default) table.
Even when using fw marks it doesn't work. I mark all packets coming
from the servers second ip address with '1' and a simple
ip ru a fwmark 1 table t_eth1
should do the job. But no way. Packets keep on getting out through ISP1
(t_eth0).
This is the real test:
10.0.2.1 is the server, 10.0.2.3 is its second ip.
10.0.2.1 = external 10.1.3.100
10.0.2.3 = external 192.168.201.3
# ip r s
192.168.201.3 via 10.0.2.3 dev eth2
10.1.3.100 via 10.0.2.1 dev eth2
10.0.2.0/24 dev eth2 proto kernel scope link src 10.0.2.2
192.168.201.0/24 dev eth1 proto kernel scope link src 192.168.201.2
10.1.3.0/24 dev eth0 proto kernel scope link src 10.1.3.101
default via 10.1.3.1 dev eth0
# ip ru s
0: from all lookup local
32762: from all fwmark 0x1 lookup t_eth1
32764: from 192.168.201.2 lookup t_eth1
32765: from 10.1.3.101 lookup t_eth0
32766: from all lookup main
32767: from all lookup default
# ip r s t t_eth0
10.0.2.0/24 dev eth2 scope link
10.1.3.0/24 dev eth0 scope link src 10.1.3.101
127.0.0.0/8 dev lo scope link
default via 10.1.3.1 dev eth0
# ip r s t t_eth1
10.0.2.0/24 dev eth2 scope link
192.168.201.0/24 dev eth1 scope link src 192.168.201.2
127.0.0.0/8 dev lo scope link
default via 192.168.201.1 dev eth1
Any hints are welcome...
btw: iproute2-ss06011, kernel 2.6.16.2, iptables 1.3.5
R.
--
___________________________________________________________________
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.
+------------------------------------------------------------------+
| Richard Lucassen, Utrecht |
| Public key and email address: |
| http://www.lucassen.org/mail-pubkey.html |
+------------------------------------------------------------------+
--
___________________________________________________________________
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.
+------------------------------------------------------------------+
| Richard Lucassen, Utrecht |
| Public key and email address: |
| http://www.lucassen.org/mail-pubkey.html |
+------------------------------------------------------------------+
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
^ permalink raw reply
* Re: Black box flight recorder for Linux
From: Matti Aarnio @ 2006-04-08 17:30 UTC (permalink / raw)
To: James Courtier-Dutton; +Cc: linux list
In-Reply-To: <44379AB8.6050808@superbug.co.uk>
On Sat, Apr 08, 2006 at 12:12:56PM +0100, James Courtier-Dutton wrote:
> Hi,
>
> I have had an idea for a black box flight recorder type feature for
> Linux. Before I try to implement it, I just wish to ask here if anyone
> has already tried it, and whether the idea works or not.
>
> Description for feature:
> Stamp the dmesg output on RAM somewhere, so that after a reset (reset
> button pressed, not power off), the RAM can be read and details of
> oopses etc. can be read.
The idea of dmesg buffer comes to Linux from SunOS 4.x series
on hardware, where system boot code explicitely left aside memory
space which was not _cleared_ during boot (it was parity-regenerated,
though). The command to display that ring-buffer content was (no
surprise there?) "dmesg".
I do wish so many things from PC hardware, but it has stayed so b***y
inferior to real computers forever. Lattest AMD CPUs have nice
features making them almost as good as IBM S/370 from early 1970es,
but still BIOSes are rather primitive things keeping things back.
( IOMMUs are things that have been invented since, and are definitely
a good thing. Otherwise it has been faster and more capacitious
processing and memory at cheaper system cost... )
Like others have noted, display card memory spaces have been used
for this kind of "survives over reset" uses -- I do also know some
embedded boot codes that created similar ring buffers for similar
reasons. They don't generally survive over power-cycling, of course.
> The main advantage of something like this would be for newer
> motherboards that are around now that don't have a serial port.
>
> If no one has tried this, I will spend some time testing.
>
> James
/Matti Aarnio
^ permalink raw reply
* Re: [PATCH rc1-mm] de_thread: fix deadlockable process addition
From: Oleg Nesterov @ 2006-04-08 21:23 UTC (permalink / raw)
To: Eric W. Biederman; +Cc: Andrew Morton, linux-kernel
In-Reply-To: <20060408211308.GA1845@oleg>
On 04/09, Oleg Nesterov wrote:
>
> proc_task_readdir:
>
> first_tid() returns old_leader
>
> next_tid() returns new_leader
>
> de_thread:
> old_leader->group_leader = new_leader;
>
>
> next_rid() returns old_leader again,
> because it is not thread_group_leader()
> anymore
I think something like this for next_tid() is sufficient:
- if (thread_group_leader(pos))
+ if (pos->pid == pos->tgid)
We can also do the same change in first_tgid().
Oleg.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.