search for: ainfo

...${pngnpbx_abc_id}/dloc/state)=${state_}); Set(DB(pngnpbx/abc/cb/${pngnpbx_abc_id}/dloc/zip)=${zip_}); return; } /* PUBLIC */ /* The "ai" macro is to add additional information to the street address. */ macro pngnpbx-abc-ai(info_) { Set(DB(pngnpbx/abc/cb/${pngnpbx_abc_id}/dloc/ainfo)=${info_}); return; } /* PUBLIC */ /* The "reentry" macro is for dynamic callback number mapping. */ macro pngnpbx-abc-reentry(position_,didcid_,abcloadingonly_) { Set(dynodid=${FILTER(a-zA-Z0-9,${didcid_})}); Set(ogcaller=${DB(pngnpbx/abc/dynodid/ogcaller/${dynodid})});...

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

Biggest change is to switch the new DTB node to /xen-core-devices instead of /xen at Stefano''s request. I also dropped the few patches title HACK etc which weren''t supposed to be there and fixed up some bits and pieces which folks commented on. George, WRT the freeze I think this is functionality which we cannot ship Xen 4.4 without. The impact is entirely constrained to the

Hi. I have xen xen-3.0.4_1 If tls in not disabled I am getting the following: ***************************************************************   ***************************************************************   ** WARNING: Currently emulating unsupported memory accesses  **   **          in /lib/tls glibc libraries. The emulation is    **   **          slow. To ensure full performance you

Hi, folks, I''m attempting to run an e-mail server on Xen. The e-mail system is Novell GroupWise, and it serves about 250 users. The disk volume for the e-mail is on my SAN, and I''ve attached the FC LUN to my Xen host, then used the "phy:/dev..." method to forward the disk through to the domU. I''m running into an issue with high I/O wait on the box (~250%)