PRIVATE MAIL | 8 Feb 20:55
Picon
Gravatar

Greetings


Good-day.

This is a personal email directed to you for your consideration alone, I request that it remain and be
treated as such only. Please bear with me for now and do not ask my name. I am a banker with HSBC in the Malta. I
have an interesting business proposal for you that will be of immense benefit to both of us. Although this
may be hard for you to believe, we stand to gain 7.2 million USD between us in a matter of days. Please grant me
the benefit of doubt and hear me out. I need you to signify your interest by replying to this email.

Most importantly, I will need you to promise to keep whatever you learn from me between us even if you decide
not to go along with me. I will make more details available to you on receipt of a positive response from you.
Do contact me only at my private emailaddress:privatepot5 <at> live.co.uk

Warm regard from Malta.

Yinghai Lu | 5 Feb 07:57
Favicon

[PATCH -v5 0/24] PCI: allocate pci bus num range for unassigned bridge busn + pci rescan cleanup

cdef5a1: PCI: clean up rescan_bus_bridge_resize
7b6deb4: PCI: make pci_rescan_bus_bridge_resize use pci_scan_bridge instead
876bd4a: PCI: Add pci_bus_add_single_device()
6e5f346: PCI, sysfs: create rescan_bridge under /sys/.../pci/devices/... for pci bridges
3c92113: PCI, sys: Use device_type and attr_groups with pci dev
e6d3c54: PCI, pciehp: Remove not needed bus number range checking
2306e31: PCI: Double checking setting for bus register and bus struct.
daddc90: pcmcia: remove workaround for fixing pci parent bus subordinate
6a88939: PCI: Seperate child bus scanning to two passes overall
60c7d94: PCI: kill pci_fixup_parent_subordinate_busnr()
e9e72be: PCI: Allocate bus range instead of use max blindly
f22af7f: PCI: Strict checking of valid range for bridge
8656ea6: PCI: Probe safe range that we can use for unassigned bridge.
4023fc3: PCI: Add pci_bus_extend/shrink_top()
a066c95: PCI, parisc: Register busn_res for root buses
d069fbb: PCI, powerpc: Register busn_res for root buses
f00e514: PCI, ia64: Register busn_res for root buses
1a203f1: PCI, x86: Register busn_res for root buses
8b1b01b: PCI: Add busn_res tracking in core
a9ccca7: PCI: add /proc/iobusn
ec1cdb3: PCI: Add busn_res operation functions
2a09fbd: Make %pR could handle bus resource with domain
9c83a59: PCI: add busn inline helper
b18cd6a: PCI: Add iobusn_resource

Set up iobusn_resource tree, and register bus number range to it.
Later when need to find bus range, will try to allocate from the tree

Need to test on arches other than x86. esp for ia64 and powerpc that support
  more than on peer root buses.
(Continue reading)

Yinghai Lu | 5 Feb 07:54
Favicon

[PATCH -v2 0/9] PCI : bridge resource reallocation patchset -- followup

c16c722: PCI: only enable pci realloc when SRIOV bar is not assigned
868faa5: PCI: print out suggestion about using pci=realloc
ace6e3c: PCI: Make pci bridge reallocating enabled/disabled
3cf1011: PCI: Retry on type IORESOURCE_IO allocation.
b6d30ee: PCI: Skip reset cardbus assigned resource during pci bus rescan
2bc1cf0: PCI: Fix cardbus bridge resources as optional size handling
e6c495b: PCI: Disable cardbus bridge MEM1 pref CTL
d1e2d75: PCI: Fix /sys warning when sriov enabled card is hot removed
29834f2: pci: Fix pci cardbus removal

are left over after Jesse pickup more of them.
it will try to auto detect if need to use pci=realloc, and print out suggestion.

including fixing some pci carbus handling.

could get from

	git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci3

-v2: add two patches before, it will fix pci cardbus removal, and srov removal
	warning
	the first one should be with v3.3.

Thanks

Yinghai

 Documentation/kernel-parameters.txt |    8 ++-
 drivers/pci/iov.c                   |    7 ++-
 drivers/pci/pci.c                   |    4 +-
(Continue reading)

Yinghai Lu | 2 Feb 21:15
Favicon

[PATCH] pci: Fix pci cardbus removal

During test busn_res allocation with cardbus, found pci card removal is not
working anymore, and it turns out it is broken by:

|commit 79cc9601c3e42b4f0650fe7e69132ebce7ab48f9
|Date:   Tue Nov 22 21:06:53 2011 -0800
|
|    PCI: Only call pci_stop_bus_device() one time for child devices at remove

that patch changed pci_remove_behind_bridge behavoir that yenta_carbus depends.

Restore the behavoir by:
1. rename pci_remove_behind_bridge to __pci_remove_behind_bridge, and let
	__pci_remove_bus_device() call it instead.
2. add pci-stop_befind_bridge that will stop device under bridge
3. add back new pci_remove_behind_bridge that will stop and remove device
	under bridge.

This one is for v3.3

Signed-off-by: Yinghai Lu <yinghai <at> kernel.org>

---
 drivers/pci/remove.c |   28 ++++++++++++++++++++++------
 1 file changed, 22 insertions(+), 6 deletions(-)

Index: linux-2.6/drivers/pci/remove.c
===================================================================
--- linux-2.6.orig/drivers/pci/remove.c
+++ linux-2.6/drivers/pci/remove.c
@@ -78,6 +78,7 @@ void pci_remove_bus(struct pci_bus *pci_
(Continue reading)

Picon

[BUGFIX][PATCH] pci: set pci sriov page size before reading SRIOV BAR

Hi Jesse,

The following patch fixes a regression introduced when an SRIOV card
is used as a PF in a 64k base page size configuration.

Reference: https://lkml.org/lkml/2012/2/1/165

Please queue this bugfix patch for the current release cycle.

Thanks,
Vaidy
---

    pci: set pci sriov page size before reading SRIOV BAR

    For an SRIOV device, PCI_SRIOV_SYS_PGSIZE should be set before
    the PCI_SRIOV_BAR are queried.  The sys pagesize defaults to 4k,
    so this change is required on powerpc box with 64k base page size.

    This is a regression caused due to moving SRIOV init to sriov_enable().

    | commit afd24ece5c76af87f6fc477f2747b83a764f161c
    | Author: Ram Pai <linuxram <at> us.ibm.com>

    | PCI: delay configuration of SRIOV capability
    | The SRIOV capability, namely page size and total_vfs of a device are
    | configured during enumeration phase of the device.  This can potentially
    | interfere with the PCI operations of the platform, if the IOV capability
    | of the device is not enabled.

(Continue reading)

MUNEDA Takahiro | 2 Feb 17:09
Favicon

[PATCH v5] Add pcie_hp=nomsi to disable MSI/MSI-X for pciehp driver

Not to use MSI/MSI-X for pciehp, add a kernel parameter, pcie_hp=nomsi.

In my environment, while shutting down, following stack trace is shown
sometimes.

  irq 16: nobody cared (try booting with the "irqpoll" option)
  Pid: 1081, comm: reboot Not tainted 3.2.0 #1
  Call Trace:
   <IRQ>  [<ffffffff810cec1d>] __report_bad_irq+0x3d/0xe0
   [<ffffffff810cee1c>] note_interrupt+0x15c/0x210
   [<ffffffff810cc485>] handle_irq_event_percpu+0xb5/0x210
   [<ffffffff810cc621>] handle_irq_event+0x41/0x70
   [<ffffffff810cf675>] handle_fasteoi_irq+0x55/0xc0
   [<ffffffff81015356>] handle_irq+0x46/0xb0
   [<ffffffff814fbe9d>] do_IRQ+0x5d/0xe0
   [<ffffffff814f146e>] common_interrupt+0x6e/0x6e
   [<ffffffff8106b040>] ? __do_softirq+0x60/0x210
   [<ffffffff8108aeb1>] ? hrtimer_interrupt+0x151/0x240
   [<ffffffff814fb5ec>] call_softirq+0x1c/0x30
   [<ffffffff810152d5>] do_softirq+0x65/0xa0
   [<ffffffff8106ae9d>] irq_exit+0xbd/0xe0
   [<ffffffff814fbf8e>] smp_apic_timer_interrupt+0x6e/0x99
   [<ffffffff814f9e5e>] apic_timer_interrupt+0x6e/0x80
   <EOI>  [<ffffffff814f0fb1>] ? _raw_spin_unlock_irqrestore+0x11/0x20
   [<ffffffff812629fc>] pci_bus_write_config_word+0x6c/0x80
   [<ffffffff81266fc2>] pci_intx+0x52/0xa0
   [<ffffffff8127de3d>] pci_intx_for_msi+0x1d/0x30
  [<ffffffff8127e4fb>] pci_msi_shutdown+0x7b/0x110
   [<ffffffff81269d34>] pci_device_shutdown+0x34/0x50
   [<ffffffff81326c4f>] device_shutdown+0x2f/0x140
(Continue reading)

Fischer, Anna | 2 Feb 12:05
Picon
Favicon

PCI MSI-X vectors in /proc/interrupts

I'm developing a kernel device driver which is using 2 PCI MSI-X vectors. 

When the device comes up and I call pci_enable_msix() the kernel prints 

"[snip] irq 45 for MSI/MSI-X"
"[snip] irq 46 for MSI/MSI-X"

So it seems as if IRQs 45 and 46 are allocated for my device. However, when I look into /proc/interrupts, it
lists my device under IRQ 42 and 43. Is it expected that those IRQ numbers match, e.g. something is broken in
my device driver or kernel code? I use Linux 3.2.0-rc7.

Thanks for your help.

Anna
OXFAM GB -UK | 31 Jan 05:04
Gravatar

Oxfam gb -uk Cash\Grant Donation 2012!!


This is to notify you that you have been officially chosen by the  
Board of Trustees of the Oxfam GB (NGO UK) as one of the final  
Recipients of a
Cash Grant/Donation of £850,000.00 grant entitlements, for more  
information on your claims contact the National Secretary Oxfam GB  
UK), Dr.Terry  
Williams.Email:(enquiry_terrywilliams0211001 <at> w.cn)Qualification  
Number(OG/N231/E101/B)

----------------------------------------------------------------
Mensaje enviado usando correoweb http://www.calipso.com.co

Mike Frysinger | 31 Jan 16:56
Picon
Favicon
Gravatar

[PATCH] update-pciids: fix PCI_COMPRESSED_IDS value when zlib is disabled

If you build with zlib disabled, then PCI_COMPRESSED_IDS is not defined,
which generates the line in the update script:
	PCI_COMPRESSED_IDS=
which in turn causes the update script to warn:
	bash: [: : integer expression expected

So default it to 0 to avoid that logic.

Reported-by: AlphatPC <at> gmail.com
Signed-off-by: Mike Frysinger <vapier <at> gentoo.org>
---
 Makefile |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/Makefile b/Makefile
index d5ed7ac..86fb0c7 100644
--- a/Makefile
+++ b/Makefile
@@ -77,6 +77,7 @@ ls-map.o: ls-map.c $(LSPCIINC)
 setpci.o: setpci.c pciutils.h $(PCIINC)
 common.o: common.c pciutils.h $(PCIINC)

+PCI_COMPRESSED_IDS ?= 0
 update-pciids: update-pciids.sh
 	sed <$< >$@ "s@^DEST=.*@DEST=$(IDSDIR)/$(PCI_IDS)@;s@^PCI_COMPRESSED_IDS=.*@PCI_COMPRESSED_IDS=$(PCI_COMPRESSED_IDS)@"
 	chmod +x $@
--

-- 
1.7.8.4

(Continue reading)

Mike Frysinger | 31 Jan 16:50
Picon
Favicon
Gravatar

[PATCH] lib/configure: match all freebsd os's

From: Marek Cruz <programatorfreez <at> gmail.com>

When using targets like "i686-pc-freebsd7.1", the configure script fails
to match for the freebsd target because it only expects "freebsd".  Add
a glob to match all freebsd targets.
---
 lib/configure |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/lib/configure b/lib/configure
index 4ae20d4..ec8eca3 100755
--- a/lib/configure
+++ b/lib/configure
@@ -86,7 +86,7 @@ case $sys in
 		esac
 		echo >>$c '#define PCI_HAVE_STDINT_H'
 		;;
-	freebsd)
+	freebsd*)
 		echo_n " fbsd-device"
 		echo >>$c '#define PCI_HAVE_PM_FBSD_DEVICE'
 		echo >>$c '#define PCI_PATH_FBSD_DEVICE "/dev/pci"'
--

-- 
1.7.8.4

Mike Frysinger | 31 Jan 16:50
Picon
Favicon
Gravatar

[PATCH] install: split out pcilib install to a dedicated target

From: Kevin Pyle <gentoo <at> spamgourmet.com>

The "install" target manages one set of files, and the "install-pcilib"
target manages a different set.  They both install the pci library though
so if you try to run `make -j install install-pcilib`, things randomly
fail.  So split out the commonly installed files into a dedicated target.
---
 Makefile |   14 +++++++++-----
 1 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/Makefile b/Makefile
index f726e87..d5ed7ac 100644
--- a/Makefile
+++ b/Makefile
@@ -98,6 +98,13 @@ clean:

 distclean: clean

+install-pcilib: lib/$(PCILIB)
+	$(DIRINSTALL) -m 755 $(DESTDIR)$(LIBDIR)
+	$(INSTALL) -c -m 644 lib/$(PCILIB) $(DESTDIR)$(LIBDIR)
+
+ifeq ($(SHARED),yes)
+install: install-pcilib
+endif
 install: all
 # -c is ignored on Linux, but required on FreeBSD
 	$(DIRINSTALL) -m 755 $(DESTDIR)$(SBINDIR) $(DESTDIR)$(IDSDIR) $(DESTDIR)$(MANDIR)/man8 $(DESTDIR)$(MANDIR)/man7
@@ -107,15 +114,12 @@ install: all
 	$(INSTALL) -c -m 644 lspci.8 setpci.8 update-pciids.8 $(DESTDIR)$(MANDIR)/man8
(Continue reading)


Gmane