Displaying 5 results from an estimated 5 matches for "table_base".
2010 Feb 26
0
[Xen-devel] Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686) / bugfix patch
...>>> George Dunlap <George.Dunlap at eu.citrix.com> 25.02.10 13:13 >>>
>>>Any suggestions for a simple fix I can try to push upstream?
>>
>> I'm afraid not (other than simply disabling at least the MSI-X part of
>> the code), as it would require table_base to be initialized properly.
>>
>> Jan
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel at lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
diff -u -r build_i386_xen_686/drivers/p...
2010 Feb 25
0
[Xen-devel] Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686) / bugfix patches
...f a machine
address from Dom0 to Xen implies that Dom0 knows what it does,
and Xen trusts it. Specifically, struct physdev_map_pirq has this
contents according to the trace
.domid = 00007ff0
.type = 00000000
.index = ffffffff
.pirq = ffffffff
.bus = 00000000
.devfn = 00000008
.entry_nr = 00000000
.table_base = f5861e4a00000001
table_base would seem like not having been initialized at all. I
would guess that they use the structure definition from before
c/s 18323 (which had, instead of a table_base member, an
int field indicating MSI vs. MSI-X. The original definition was
added with c/s 17534 and 17535...
2010 Oct 08
17
MSI badness in xen-unstable
Hi,
I''ve been trying to boot stefano''s minimal dom0 kernel from
git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git
2.6.36-rc1-initial-domain-v2+pat
On xen-unstable, I get the following WARN_ON()''s from Xen when bringing
up the NIC''s, then the machine hangs forever when trying to login either
over serial or NIC.
(XEN) Xen WARN at msi.c:649
(XEN) ----[
2020 Aug 10
2
(wasm-ld) Any fundamental problems with linking a shared wasm library statically?
...e + <offset> = <address of symbol> +
<constant>`. The RHS can also be `<table base> + constant`. So I think it could
be run at link time.
Alternatively, I think we could run $__wasm_call_ctors as first thing in a
linker-generated main function after updating memory_base and table_base of the
imported module and it'd apply the relocations.
Would this make sense? I'm new at wasm and not too experienced in linking (just
a happy user of ld.lld and gold) so it's possible that I'm missing something and
this is not going to work.
Thanks,
Ă–mer
2008 Sep 17
7
Megaraid SAS driver failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3
On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller) driver is not loading correctly if vtd support in Xen is enabled.
It fails at the point of initializing firmware.
I wasn''t seeing this error with Xen-3.2.2-rc3 (Unstable version), though with vtd disabled in Xen-3.3.0, it is working.
Looks like a degrade problem.
Any clues?
Thx,
Venkat