similar to: Wireless VoIP

Hello there! I made Debian, Xen 2.0 and CLUSTER/GFS work together :). I wrote this little tutorial to help you setup yours. Any feedback is welcome, except comments about W3C validation of my code :p Note that I am talking about compiling CLUSTER with your XEN kernel, I don''t explain how to setup a working cluster. You can find how to setup those in official RedHat docs. You will see,

Hello, I''m setting up a Xen system since I have diferent choices to create the domU''s partitions: raw partition, lvm, files. I''ve done some tests with hdparm and it all seems to be the same. Can anyone, please, share with me what if the best method. Best regards, Luis _______________________________________________ Xen-users mailing list

Hi guys, Another strange behavior with some test servers. They are booted using 2.6.11.12, xen-2.0.6, Debian. The only daemons running on dom0 are : xend, smtp, quagga (ospf), portmap (nfs client), sshd. Memory usage at startup is aroung 30 MB. Dom0 reserved memory is 256 MB. The only things that happen on this server are domU''s start/stop (xm create, xm shutdown) and a

> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of > Davide Italiano via llvm-dev > Sent: Thursday, September 20, 2018 10:55 AM > To: ramana.venkat83 at gmail.com; Cary Coutant > Cc: llvm-dev; LLDB > Subject: Re: [llvm-dev] [lldb-dev] [LLD] How to get rid of debug info of > sections deleted by garbage collector > >

On 19.11.2020 03:21, Cary Coutant wrote: >>> If the .debug_str section *by itself* exceeds 4GB, then yes any string >>> with a 32-bit reference to it must be in the first 4GB. Strings that >>> have only 64-bit references to them can be sorted to the end of the >>> section, if necessary. I wouldn't think anyone guarantees or cares >>> about the

I observed a strange networking behaviour of my Debian virtual host in function of the MAC address I use. It seems that when I use an existing constructor code, networking works without any problem, but is impossible in the other case... Ex. : - vif = [ ''mac=aa:00:00:00:00:55, bridge=xen-br0'' ] -> no problem - vif = [ ''mac=df:00:00:00:00:55,

Thank you all for your time in responding to my query. My understanding was also similar to what you all mentioned here but wanted to check if there are any recent developments in solving this problem. Thanks, Ramana On Thu, Sep 20, 2018 at 9:32 PM, Rui Ueyama <ruiu at google.com> wrote: > Right. Technically we can get rid of debug info that corresponds to dead > sections, but in

Hi! Currently Clang "-g" flag emits full debug info, which is fine for debugging, but increases the binary size significantly. It may be useful to produce less debug info, that is still enough for collecting nice stack traces with file names and line numbers, but would introduce less overhead. Cary Coutant made a patch which does this for GCC (it didn't hit trunk yet) - reduces

On Jan 7, 2018 5:02 PM, "Cary Coutant via llvm-dev" <llvm-dev at lists.llvm.org> wrote: > I think we all agree that blindly allowing the linker to honor the options > would be scary. I agree that we should whitelist the options, and am of the > opinion that we should force validation on the linker side (use of any > option which the linker doesn't support in this

Hi, After compiling an example.cpp file with "-c -ffunction-sections" and linking with "--gc-sections" (used ld.lld), I am still seeing debug info for the sections deleted by garbage collector in the generated executable. Are there any compiler/linker options and/or other tools in LLVM to get rid of the above mentioned unneeded debug info? If such options does not exist,

On 8 January 2018 at 08:14, Rui Ueyama <ruiu at google.com> wrote: > On Mon, Jan 8, 2018 at 3:55 AM, Sean Silva via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >> >> On Jan 7, 2018 5:02 PM, "Cary Coutant via llvm-dev" < >> llvm-dev at lists.llvm.org> wrote: >> >> > I think we all agree that blindly allowing the

How i can classify sip traffic (voip)?? I try dst 5060 udp port, but dont''work. sip sesion use dynamic port. Sniffing packets with windows net-peeker, I see that packets lenghts is always=87 How i can filter, by packet lenght, with u32? Regards Fabian

> On Jan 7, 2018, at 5:02 PM, Cary Coutant <ccoutant at gmail.com> wrote: > >> I think we all agree that blindly allowing the linker to honor the options >> would be scary. I agree that we should whitelist the options, and am of the >> opinion that we should force validation on the linker side (use of any >> option which the linker doesn't support in this

> I think we all agree that blindly allowing the linker to honor the options > would be scary. I agree that we should whitelist the options, and am of the > opinion that we should force validation on the linker side (use of any > option which the linker doesn't support in this form can be fatal). > Starting small is the best way, with `-l` and `-L` as a starting point. I >

On Mon, Jan 8, 2018 at 3:55 AM, Sean Silva via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Jan 7, 2018 5:02 PM, "Cary Coutant via llvm-dev" < > llvm-dev at lists.llvm.org> wrote: > > > I think we all agree that blindly allowing the linker to honor the > options > > would be scary. I agree that we should whitelist the options, and am

From: Sylvain Gault <sylvain.gault at gmail.com> I found something suspicious while hunting another bug a while ago. The conditions for that bug to occur seems quite hard to meet, but it's still code quality improvement. See the commit message for details. Sylvain Gault (1): efi: Suspicious size reduction in emalloc efi/main.c | 4 +--- 1 file changed, 1 insertion(+), 3

On Apr 5, 2012, at 10:24 AM, Alexey Samsonov <samsonov at google.com> wrote: > Hi! > > Currently Clang "-g" flag emits full debug info, which is fine for debugging, but increases the binary size significantly. > It may be useful to produce less debug info, that is still enough for collecting nice stack traces with file names and line numbers, > but would introduce

From: Sylvain Gault <sylvain.gault at gmail.com> I don't know if I should merge those trivial warning fix into one commit. I can reformat it as requested. Those are a few warning fixes for the efi part. The code involved has mainly been introduced in recent commits. Sylvain Gault (3): efi: fix warnings about argument types efi: fix pointer-type mismatch assigment warning efi: fix

Hi, Le ven. 10 juil. 2020 à 16:56, Sylvain Boily <sylvain at wazo.io> a écrit : > > It probably can help you: > > https://github.com/wazo-platform/wazo-provd-plugins/blob/master/plugins/xivo-jitsi/1/templates/base.tpl > > Sylvain > > Yes, provided example was exactly what I was after ! Thank you very much ! -------------- next part -------------- An HTML attachment

From: Sylvain Gault <sylvain.gault at gmail.com> TL;DR: The section aligment in linker scripts messed-up the memory mapping needed for the compression / decompression to work. The bug with gcc 5 is not trivial, I'll do my best to explain it here. Basically, there are two memory mappings of the code. One in "virtual memory", and one in "load memory". The one in