<feed xmlns='http://www.w3.org/2005/Atom'>
<title>talos-obmc-linux/drivers/lguest, branch v3.6-rc3</title>
<subtitle>Talos™ II Linux sources for OpenBMC</subtitle>
<id>https://git.raptorcs.com/git/talos-obmc-linux/atom?h=v3.6-rc3</id>
<link rel='self' href='https://git.raptorcs.com/git/talos-obmc-linux/atom?h=v3.6-rc3'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/'/>
<updated>2012-01-12T05:14:47+00:00</updated>
<entry>
<title>lguest: Make sure interrupt is allocated ok by lguest_setup_irq</title>
<updated>2012-01-12T05:14:47+00:00</updated>
<author>
<name>Stratos Psomadakis</name>
<email>psomas@cslab.ece.ntua.gr</email>
</author>
<published>2012-01-12T05:14:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=b6c96c0214138186f495e3ee73737c6fc5e4efa2'/>
<id>urn:sha1:b6c96c0214138186f495e3ee73737c6fc5e4efa2</id>
<content type='text'>
Make sure the interrupt is allocated correctly by lguest_setup_irq (check the
return value of irq_alloc_desc_at for -ENOMEM)

Signed-off-by: Stratos Psomadakis &lt;psomas@cslab.ece.ntua.gr&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt; (cleanups and commentry)
</content>
</entry>
<entry>
<title>lguest: move the lguest tool to the tools directory</title>
<updated>2012-01-12T05:14:47+00:00</updated>
<author>
<name>Davidlohr Bueso</name>
<email>dave@gnu.org</email>
</author>
<published>2012-01-12T05:14:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=07fe9977b6234ede1bd29e10e0323e478860c871'/>
<id>urn:sha1:07fe9977b6234ede1bd29e10e0323e478860c871</id>
<content type='text'>
This is a better location instead of having it in Documentation.

Signed-off-by: Davidlohr Bueso &lt;dave@gnu.org&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt; (fixed compile)
</content>
</entry>
<entry>
<title>lguest: switch segment-voodoo-numbers to readable symbols</title>
<updated>2012-01-12T05:14:47+00:00</updated>
<author>
<name>Jacek Galowicz</name>
<email>jacek@galowicz.de</email>
</author>
<published>2012-01-12T05:14:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=39082f7e5912cdc70f9ab0767e7342711f34b9f8'/>
<id>urn:sha1:39082f7e5912cdc70f9ab0767e7342711f34b9f8</id>
<content type='text'>
When studying lguest's x86 segment descriptor code, it is not longer
necessary to have the Intel x86 architecture manual open on the page
with the segment descriptor illustration to understand the crazy
numbers assigned to both descriptor structure halves a/b.
Now the struct desc_struct's fields, like suggested by
Glauber de Oliveira Costa in 2008, are used.

Signed-off-by: Jacek Galowicz &lt;jacek@galowicz.de&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>virtio: harsher barriers for rpmsg.</title>
<updated>2012-01-12T05:14:42+00:00</updated>
<author>
<name>Rusty Russell</name>
<email>rusty@rustcorp.com.au</email>
</author>
<published>2012-01-12T05:14:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=7b21e34fd1c272e3a8c3846168f2f6287a4cd72b'/>
<id>urn:sha1:7b21e34fd1c272e3a8c3846168f2f6287a4cd72b</id>
<content type='text'>
We were cheating with our barriers; using the smp ones rather than the
real device ones.  That was fine, until rpmsg came along, which is
used to talk to a real device (a non-SMP CPU).

Unfortunately, just putting back the real barriers (reverting
d57ed95d) causes a performance regression on virtio-pci.  In
particular, Amos reports netbench's TCP_RR over virtio_net CPU
utilization increased up to 35% while throughput went down by up to
14%.

By comparison, this branch is in the noise.

Reference: https://lkml.org/lkml/2011/12/11/22

Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next</title>
<updated>2012-01-07T01:22:09+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-01-07T01:22:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=9753dfe19a85e7e45a34a56f4cb2048bb4f50e27'/>
<id>urn:sha1:9753dfe19a85e7e45a34a56f4cb2048bb4f50e27</id>
<content type='text'>
* git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next: (1958 commits)
  net: pack skb_shared_info more efficiently
  net_sched: red: split red_parms into parms and vars
  net_sched: sfq: extend limits
  cnic: Improve error recovery on bnx2x devices
  cnic: Re-init dev-&gt;stats_addr after chip reset
  net_sched: Bug in netem reordering
  bna: fix sparse warnings/errors
  bna: make ethtool_ops and strings const
  xgmac: cleanups
  net: make ethtool_ops const
  vmxnet3" make ethtool ops const
  xen-netback: make ops structs const
  virtio_net: Pass gfp flags when allocating rx buffers.
  ixgbe: FCoE: Add support for ndo_get_fcoe_hbainfo() call
  netdev: FCoE: Add new ndo_get_fcoe_hbainfo() call
  igb: reset PHY after recovering from PHY power down
  igb: add basic runtime PM support
  igb: Add support for byte queue limits.
  e1000: cleanup CE4100 MDIO registers access
  e1000: unmap ce4100_gbe_mdio_base_virt in e1000_remove
  ...
</content>
</entry>
<entry>
<title>x86: Fix rflags in FAKE_STACK_FRAME</title>
<updated>2011-12-06T09:02:38+00:00</updated>
<author>
<name>Seiichi Ikarashi</name>
<email>s.ikarashi@jp.fujitsu.com</email>
</author>
<published>2011-12-06T08:58:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=1cf8343f55525c09c88da0a494a96e1b034f84e2'/>
<id>urn:sha1:1cf8343f55525c09c88da0a494a96e1b034f84e2</id>
<content type='text'>
The x86_64 kernel pushes the fake kernel stack in
arch/x86/kernel/entry_64.S:FAKE_STACK_FRAME, and
rflags register in it does not conform to the specification.

Although Intel's manual[1] says bit 1 of it shall be set to 1,
this bit is cleared to 0 on pushing the fake stack.

[1] Intel(R) 64 and IA-32 Architectures Software Developer's Manual
    Vol.1 3-21 Figure 3-8. EFLAGS Register

If it is not on purpose, it is better to be fixed, because
it can lead some tools misunderstanding the stack frame. For example,
"crash" utility[2] actually detects it and warns you like
below:

       RIP: ffffffff8005dfa2  RSP: ffff8104ce0c7f58  RFLAGS: 00000200
       [...]

       bt: WARNING: possibly bogus exception frame

Signed-off-by: Seiichi Ikarashi &lt;s.ikarashi@jp.fujitsu.com&gt;
Tested-by: Masayoshi MIZUMA &lt;m.mizuma@jp.fujitsu.com&gt;
Cc: Jan Beulich &lt;JBeulich@suse.com&gt;
Cc: Frederic Weisbecker &lt;fweisbec@gmail.com&gt;
Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>enable virtio_net to return bus_info in ethtool -i consistent with emulated NICs</title>
<updated>2011-11-16T22:26:46+00:00</updated>
<author>
<name>Rick Jones</name>
<email>rick.jones2@hp.com</email>
</author>
<published>2011-11-14T14:17:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=66846048f55c6c05a4c46c2daabb773173f8f28d'/>
<id>urn:sha1:66846048f55c6c05a4c46c2daabb773173f8f28d</id>
<content type='text'>
Add a new .bus_name to virtio_config_ops then modify virtio_net to
call through to it in an ethtool .get_drvinfo routine to report
bus_info in ethtool -i output which is consistent with other
emulated NICs and the output of lspci.

Signed-off-by: Rick Jones &lt;rick.jones2@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>lguest: add export.h to lguest files for THIS_MODULE/EXPORT_SYMBOL</title>
<updated>2011-10-31T23:32:13+00:00</updated>
<author>
<name>Paul Gortmaker</name>
<email>paul.gortmaker@windriver.com</email>
</author>
<published>2011-07-21T17:03:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=39a0e33da0189c99ed3cea6945cda1bc9f4b7b83'/>
<id>urn:sha1:39a0e33da0189c99ed3cea6945cda1bc9f4b7b83</id>
<content type='text'>
We need this in advance of the module.h cleanup, or we'll
get compile errors like this:

  CC      drivers/lguest/lguest_device.o
drivers/lguest/lguest_device.c: In function ‘lguest_devices_init’:
drivers/lguest/lguest_device.c:490: error: ‘THIS_MODULE’ undeclared (first use in this function)

Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
</content>
</entry>
<entry>
<title>lguest: move process freezing before pending signals check</title>
<updated>2011-10-27T00:26:18+00:00</updated>
<author>
<name>Michal Hocko</name>
<email>mhocko@suse.cz</email>
</author>
<published>2011-09-27T06:56:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=0acf00014bcfd71090c3b0d43c98e970108064e4'/>
<id>urn:sha1:0acf00014bcfd71090c3b0d43c98e970108064e4</id>
<content type='text'>
run_guest tries to freeze the current process after it has handled
pending interrupts and before it calls lguest_arch_run_guest.
This doesn't work nicely if the task has been killed while being frozen
and when we want to handle that signal as soon as possible.
Let's move try_to_freeze before we check for pending signal so that we
can get out of the loop as soon as possible.

Signed-off-by: Michal Hocko &lt;mhocko@suse.cz&gt;
Acked-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>lguest: Allow running under paravirt-enabled KVM.</title>
<updated>2011-10-27T00:26:17+00:00</updated>
<author>
<name>Rusty Russell</name>
<email>rusty@rustcorp.com.au</email>
</author>
<published>2011-10-27T00:26:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=b56e3215d4331bff9b6d5e5f68bc1ec5cb01e650'/>
<id>urn:sha1:b56e3215d4331bff9b6d5e5f68bc1ec5cb01e650</id>
<content type='text'>
We actually can run under KVM, as it doesn't paravirtualize anything we
need to use; reduce the check to checking we are the normal ringlevel.

Reported-by: Stefanos Geraggelos &lt;sgerag@cslab.ece.ntua.gr&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;# HG changeset patch
</content>
</entry>
</feed>
